# Remote unix monitor extensions 2.0

**URL:** <https://community.dynatrace.com/t/remote-unix-monitor-extensions-2-0/47211>\
**Category:** Extensions\
**Tags:** hosts-classic, extensions\
**Created:** [August 20, 2024, 9:00am UTC](https://community.dynatrace.com/t/remote-unix-monitor-extensions-2-0/47211 "2024-08-20T09:00:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SrikanthSamraj](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@SrikanthSamraj](https://community.dynatrace.com/u/SrikanthSamraj)\
**Post date:** [August 20, 2024, 9:00am UTC](https://community.dynatrace.com/t/remote-unix-monitor-extensions-2-0/47211/1 "2024-08-20T09:00:51Z")

</div>

Hi, there

Problems generated for remote hosts configured through Remote Unix monitor (extensions 2.0) are tagged as an environment problem rather than an entity problem. Is this an expected behavior?

Regards,

Srikanth

---

<div class="post-metadata">

**Author:** ![SrikanthSamraj](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@SrikanthSamraj](https://community.dynatrace.com/u/SrikanthSamraj)\
**Post date:** [August 21, 2024, 7:25am UTC](https://community.dynatrace.com/t/remote-unix-monitor-extensions-2-0/47211/2 "2024-08-21T07:25:08Z")

</div>

Figured this out by filling in “Dimension key of entity for events” with **dt.entity:remote\_unix:host.**

After performing this, problems are rightly getting associated with an entity rather than environment.