Skip to content

Commit a669644

Browse files
authored
Merge pull request #206638 from AbbyMSFT/patch-15
Update alerts-dynamic-thresholds.md
2 parents 9dd2fd8 + ad2b75a commit a669644

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-monitor/alerts/alerts-dynamic-thresholds.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,9 @@ When an alert rule is first created, the thresholds appearing in the chart are c
9494
If you have a new resource or missing metric data, Dynamic Thresholds won't trigger alerts before three days and at least 30 samples of metric data are available, to ensure accurate thresholds.
9595
For existing resources with sufficient metric data, Dynamic Thresholds can trigger alerts immediately.
9696

97-
## How does prolong outages affected the thresholds that are calculated?
97+
## How do prolonged outages affect the calculated thresholds?
9898

99-
Dynamic Threholds automatically recognizes prolonged outages and removes them from thresholds training. The results are thresholds that fit the data and can detect service issues with the same sensitivity as before an outage occurred.
99+
The system automatically recognizes prolonged outages and removes them from threshold learning algorithm. As a result, despite prolonged outages, dynamic thresholds understand the data. Service issues are detected with the same sensitivity as before an outage occurred.
100100

101101
## Dynamic Thresholds best practices
102102

0 commit comments

Comments
 (0)