Skip to content

Commit 5759aff

Browse files
azarboonAbbyMSFT
andauthored
Update articles/azure-monitor/alerts/alerts-overview.md
Co-authored-by: AbbyMSFT <[email protected]>
1 parent f1bbbe6 commit 5759aff

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,9 @@ This table provides a brief description of each alert type. For more information
5959

6060
Alerts can be stateful or stateless.
6161
- Stateless alerts fire each time the condition is met, even if fired previously.
62-
- Stateful alerts fire when the rule conditions are met, and will not fire again or trigger any more actions until the conditions are resolved. A stateful alert isn't fired if there's already a fired alert on a specific time series. If, for example, there are 2 alert rules with the same condition, but one has a scope at a resource level and another alert rule has a scope at a resource group level, and an alert is triggered in a time series for one of those rules, the other rule will not trigger an alert until the first alert is resolved.
62+
- Stateful alerts fire when the rule conditions are met, and will not fire again or trigger any more actions until the conditions are resolved.
63+
64+
Each alert rule is evaluated individually. There is no validation to check if there is another alert configured for the same conditions. If there is more than one alert rule configured for the same conditions, each of those alerts will fire when the conditions are met.
6365

6466
Alerts are stored for 30 days and are deleted after the 30-day retention period.
6567

0 commit comments

Comments
 (0)