You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked for previous/existing GitHub issues
Description
I have a customer requirement where several VMS are being deployed but not all VMs require Alerting. This normally is the case with Devops Runners that switch off regularly everyday at a certain period of time. Once this event happens a heartbeat alert will be fired which is not required on those VMs.
For more clarity, Consider the following example:
there are 3 Vms, 2 Vms require the alerting but the third Vm needs to be excluded.
I also looked into the Monitor Disable parameter in the Json however, this might have some limitation:
the parameter is targeting scopes meaning all VMs will be affected and in my case i only want some VMs to have alerting disabled.
In the Json itself, the Monitor Disabled isn't included within the VMs alerting
The text was updated successfully, but these errors were encountered:
Hello @MohmadEh ,
thanks for your feedback. Unfortunately, alerts cannot be disabled for a single instance or resource when targeted a bigger scopes like Subscription or resource group or LAW. What you could do in these cases is:
filter the resource in the query (not possible in AMBA)
add the resource Id of the given resource to a suppression alert processing rule
In the first case, you will not get any alert. In the latter, alert will appear in the but will not be notified.
Check for previous/existing GitHub issues
Description
I have a customer requirement where several VMS are being deployed but not all VMs require Alerting. This normally is the case with Devops Runners that switch off regularly everyday at a certain period of time. Once this event happens a heartbeat alert will be fired which is not required on those VMs.
For more clarity, Consider the following example:
there are 3 Vms, 2 Vms require the alerting but the third Vm needs to be excluded.
I also looked into the Monitor Disable parameter in the Json however, this might have some limitation:
The text was updated successfully, but these errors were encountered: