Skip to content

Commit d3fb541

Browse files
Merge pull request #50859 from ShawnKupfer/WB1811
User Feedback 440457 - Fix log search states per UUF feedback
2 parents 805530b + 7f4094b commit d3fb541

File tree

1 file changed

+2
-2
lines changed
  • learn-pr/azure/incident-response-with-alerting-on-azure/includes

1 file changed

+2
-2
lines changed

learn-pr/azure/incident-response-with-alerting-on-azure/includes/5-log-alerts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,6 @@ Consider using this type of alert when you need to add a level of tolerance to t
5050

5151
As you can see, metric measurements greatly reduce the volume of alerts that are produced. Still, give careful consideration when you're setting the threshold parameters to avoid missing critical alerts.
5252

53-
## Stateless nature of log search alerts
53+
## Log search alerts and state
5454

55-
One of the primary considerations when you're evaluating the use of log search alerts is that they're stateless (stateful log search alerts are [currently in preview](/azure/azure-monitor/alerts/alerts-types#log-alerts)). A stateless log search alert generates new alerts every time the rule criteria are triggered, regardless of whether the alert was previously recorded.
55+
Alerts can be [stateful or stateless](/azure/azure-monitor/alerts/alerts-types#log-alerts). Stateless alerts fire each time the condition is met, even if fired previously. Stateful alerts fire when the rule conditions are met, and will not fire again or trigger any more actions until the conditions are resolved.

0 commit comments

Comments
 (0)