Skip to content

Commit 3d04454

Browse files
authored
Merge pull request #57954 from v-makoud/patch-87
CC31660: Possible error at line 103
2 parents 71a28cc + 430cc62 commit 3d04454

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/monitoring-and-diagnostics/monitor-alerts-unified-log.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Now assume we have a log alert rule called *Contoso-Log-Alert*, as per configura
100100
- At 1:15 PM when Contoso-Log-Alert was executed by Azure alerts, log search result provided 2 records; exceeding the threshold and firing the alert, soon after by triggering the [action group](monitoring-action-groups.md) associated.
101101
- Now at the next iteration at 1:20 PM when Contoso-Log-Alert was executed by Azure alert, log search result provided again 0 records; below the threshold and hence not firing the alert.
102102

103-
But in the above listed case, at 1:15 PM - Azure alerts can't determine that the underlying issues seen at 1:10 persist and if there is net new failures; as query provided by user may be taking into account earlier records - Azure alerts can't be sure. Hence to err on the side of caution, Contoso-Log-Alert is fired again at 1:15 PM via configured [action group](monitoring-action-groups.md). Now at 1:20 PM when no records are seen - Azure alerts can't be certain that the cause of the records has been solved; hence Contoso-Log-Alert will not changed to Resolved in Azure Alert dashboard and/or notifications sent out stating resolution of alert.
103+
But in the above listed case, at 1:15 PM - Azure alerts can't determine that the underlying issues seen at 1:10 persist and if there is net new failures; as query provided by user may be taking into account earlier records - Azure alerts can be sure. Hence to err on the side of caution, when Contoso-Log-Alert is executed at 1:15 PM, configured [action group](monitoring-action-groups.md) is fired again. Now at 1:20 PM when no records are seen - Azure alerts can't be certain that the cause of the records has been solved; hence Contoso-Log-Alert will not changed to Resolved in Azure Alert dashboard and/or notifications sent out stating resolution of alert.
104104

105105

106106
## Pricing and Billing of Log Alerts

0 commit comments

Comments
 (0)