Add ability to Resolve Query Based Alert
Hi. As for today, query based alert cannot be Resolved at all. Not manually and not by a "good" result. For example, a metric measurement alert rule Fired alert when "Greater Then 10". When the result is less or equal than 10, alert should be Resolved.
We are currently working on this capability.
Fem Canlas commented
Hello, Were there any updates from this?
This is currently a problem for our team.
Can someone provide a status update on this? It's been 315 days since someone mentioned that this capability is being worked on.
Rashmi Gupta commented
Hello, I am facing same issue for a log based alert. The alarm is fired but not resolved even when the condition is not met.
Is there any update on this issue?
Hi Azure Alerts team,
would it be possible to share with us a roadmap or a work item for this feature or could you gave some information when this feature could be available?
We need this information to decide how much time we invest in some intermediate/temporary solution.
Luis Rodrigues commented
please do it has soon has you can this is a deal breaker.
I think we need to develop logic to autoclose the alert .
For example, I setup the alert rule to send notification if particular service is not running. And now, I want to auto close this alert when service change its state to running.
Shea Woolnough commented
I am really glad to see this has been started, is there any timeline or update when this might be available, or released in preview mode?
As others have mentioned, implementing this would be really useful. Especially since the alert schema used for webhooks mentions that monitorCondition is an essential field & it can have the Resolved value.
Hi, I am facing the same issue. I have set a metric alert and in action item using Azure Runbook.
Whenever the alert is triggered, it is triggering the runbook twice, once when fired and other when alert is resolved
Can I get some solution for this
We are needing this feature too. There are any updates for this?
When will this be implemented?
Yosbel Esperón González commented
The documentation says:
Log alert rules comprise of custom query-based logic provided by users and hence without a resolved state. Due to which every time the conditions specified in the log alert rule are met, it is fired.
It would be nice if there were a possibility that if the alert is fired, and the next time the query is executed it does not satisfy the condition to be fired again, then a resolved alert could be sent.