# Azure Scale Set VM monitoring: How to deal with host or monitoring unavailable?

**URL:** <https://community.dynatrace.com/t/azure-scale-set-vm-monitoring-how-to-deal-with-host-or-monitoring-unavailable/44944>\
**Category:** Alerting\
**Tags:** azure, hosts-classic, problems-classic\
**Created:** [April 2, 2024, 12:09pm UTC](https://community.dynatrace.com/t/azure-scale-set-vm-monitoring-how-to-deal-with-host-or-monitoring-unavailable/44944 "2024-04-02T12:09:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rsmsdk](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@rsmsdk](https://community.dynatrace.com/u/rsmsdk)\
**Post date:** [April 2, 2024, 12:09pm UTC](https://community.dynatrace.com/t/azure-scale-set-vm-monitoring-how-to-deal-with-host-or-monitoring-unavailable/44944/1 "2024-04-02T12:09:23Z")

</div>

Hi

I apologize if this is a generic questions.

We have configured Dynatrace monitoring of an Azure Scale Set where we get alerts for **“Host or monitoring unavailable”** everytime a VM is shut down automatically.

The problems stick and have to be removed manually.

This alerting add confusion for our Ops team, since the VM naming is dynamic and different everytime a new VM is added /removed by the&nbsp;defined schedule.

How does other deal with alerting and monitoring of Scale Sets?

I’m not part of the Azure team internally, so if configuration should be different on that side, any valid questions is valued.

Thank you.

---

<div class="post-metadata">

**Author:** ![mizso74](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@mizso74](https://community.dynatrace.com/u/mizso74)\
**Post date:** [April 2, 2024, 9:28pm UTC](https://community.dynatrace.com/t/azure-scale-set-vm-monitoring-how-to-deal-with-host-or-monitoring-unavailable/44944/2 "2024-04-02T21:28:24Z")

</div>

Hi&nbsp;[@rsmsdk](https://community.dynatrace.com/user/42071),

I am a little bit confused regarding your post. You metioned both: problems and alerts. I do not have solution for problem view. Regarding alerting you can define an alerting profile for AWS with an event filter, so if your DT is integrated with an ITSM tool eg SNOW or Opsgenie you will receive tickets / alets from AWS except “Host or monitoring unavailable”:

 ![Mizs_1-1712093135582.png](https://global.discourse-cdn.com/dynatrace/original/2X/1/1baa23b92ee6930e41bb1ff402cfac3d6f3746f1.png)

I hope it helps.

Best regards,

Mizső

---

<div class="post-metadata">

**Author:** ![rsmsdk](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@rsmsdk](https://community.dynatrace.com/u/rsmsdk)\
**Post date:** [April 3, 2024, 6:54am UTC](https://community.dynatrace.com/t/azure-scale-set-vm-monitoring-how-to-deal-with-host-or-monitoring-unavailable/44944/3 "2024-04-03T06:54:24Z")

</div>

Sorry about the confusion, we receive alerts for these problems, but I obviously need to be clear here.

The thing is that we want to receive alerts for host or monitoring unavailable, but the nature of scale sets from my experience, seem to be random host names appearing and disappearing with new hostnames each times. The nature of this causes alot of host unavailable by design, and I was wondering how other people deal with it.

---

<div class="post-metadata">

**Author:** ![AntonPineiro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antonpineiro/32/49_2.png) [@AntonPineiro](https://community.dynatrace.com/u/AntonPineiro)\
**Post date:** [April 3, 2024, 7:36am UTC](https://community.dynatrace.com/t/azure-scale-set-vm-monitoring-how-to-deal-with-host-or-monitoring-unavailable/44944/4 "2024-04-03T07:36:33Z")

</div>

Hi,

You can&nbsp;[adjust the sensitivity of anomaly detection for infrastructure](https://docs.dynatrace.com/docs/shortlink/problem-detection-sensitivity-infrastructure)&nbsp;base on your needs.

Best regards