Skip to content

Commit f6a18fc

Browse files
authored
Updated the time to resolve behavior in stateful log alerts
1 parent 5fd5f91 commit f6a18fc

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

articles/azure-monitor/alerts/alerts-overview.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -78,10 +78,13 @@ You can configure whether log or metric alerts are stateful or stateless. Activi
7878
- Stateful alerts fire when the condition is met and then don't fire again or trigger any more actions until the conditions are resolved.
7979
For stateful alerts, the alert is considered resolved when:
8080

81-
|Alert type |The alert is resolved when |
82-
|---------|---------|
83-
|Metric alerts|The alert condition isn't met for three consecutive checks.|
84-
|Log alerts|The alert condition isn't met for 30 minutes for a specific evaluation period (to account for log ingestion delay), and <br>the alert condition isn't met for three consecutive checks.|
81+
|Alert type|Alert rule frequency|The alert is resolved when|
82+
|---------|---------|---------|
83+
|Metric alerts|All frequencies|The alert condition isn't met for three consecutive checks.|
84+
|Log alerts|1-minute frequency|The alert condition isn't met for 10 minutes.|
85+
|Log alerts|5 to 15 minutes frequencies|The alert condition isn't met for three frequency periods.|
86+
|Log alerts|15 minutes to 11 hours frequencies|The alert condition isn't met for two frequency periods.|
87+
|Log alerts|11 hours frequency or more|The alert condition isn't met for one frequency period.|
8588

8689
When the alert is considered resolved, the alert rule sends out a resolved notification using webhooks or email and the monitor state in the Azure portal is set to resolved.
8790

0 commit comments

Comments
 (0)