Skip to content

Commit 1f62d49

Browse files
authored
Update alerts-overview.md
1 parent d2d07b3 commit 1f62d49

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

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

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -59,14 +59,10 @@ 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.
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. Stateful alerts aren't fired if there's already a fired alert on a specific time series. This is the case even if more than one stateful alerts have been applied on different scopes for the same condition, for example scoped on resource level and resource group level.
6363

6464
Alerts are stored for 30 days and are deleted after the 30-day retention period.
6565

66-
> [!NOTE]
67-
> Metric alerts are stateful by default, so other alerts aren't fired if there's already a fired alert on a specific time series. This is the case even if more than one metric alert has been applied on different scopes, for example on resource level and resource group level.
68-
69-
7066
### Stateless alerts
7167
Stateless alerts fire each time the condition is met. The alert condition for all stateless alerts is always `fired`.
7268

0 commit comments

Comments
 (0)