Skip to content

Commit 418c860

Browse files
authored
Update metric-alert-config.mdx
updated text for responsiveness
1 parent e46b440 commit 418c860

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/product/alerts/create-alerts/metric-alert-config.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Change alerts, or alerts that use a percent change threshold, are useful when yo
134134

135135
Anomaly alerts automatically detect trends outside expected values. They can be especially helpful for spiky or seasonal data that are too noisy for static or percentage based thresholds. Sentry will look at historical data for the given metric and determine if the current data is anomalous. Certain metrics, like Apdex, are currently not supported for anomaly alerts.
136136

137-
You have three options for the responsiveness of the alert: low, medium, and high. Low responsiveness means the alert will fire less frequently with each instance being higher signal. High responsiveness will capture more instances of the alert, which creates more coverage with a greater likelihood for false positives. Our recommendation is to start with our default (medium), and iterate based on the results you see.
137+
You have three options for the responsiveness of the alert: low, medium, and high. Low responsiveness means the alert will fire less frequently with each instance having higher confidence of being a problem. High responsiveness will capture more instances of the alert, which creates more coverage with a greater likelihood for false positives. Our recommendation is to start with our default (medium), and iterate based on the results you see.
138138

139139
Another setting is to set the direction of the alert: above and/or below the expected bounds. This setting can help increase the signal of your alert rule.
140140

0 commit comments

Comments
 (0)