0
Use the original baseline for % based alerts
Source: getsentry/sentry#66476 · opened by @rachrwang
Environment SaaS ([ Steps to Reproduce Today, %-based metric alerts use the prior interval as the baseline, which means that at any moment, it'll auto-resolve even if the regression is still live, if there's no change from the prior interval. For example, if I've set up a metric alert for 15-min interval, it'll auto-resolve 15 minutes after firing if there's no change from the prior interval. The more accurate baseline is the original interval that triggered the alert. Expected Result The baseline for the metric alert is based on the original data that triggered the alert. Actual Result Recommended fix: • Use % comparison to trigger the alert • Use the % comparison to convert to a number-based threshold • For example - let's say my trigger is 20% change for same time in a week. If on Monday, 3/1 at 9am, I see that my alert triggers b/c count goes from 200 to 220 week over week, on 3/8, if the count is still at 220, I don't …
No pledges yet. Be the first to back this.
Comments
Similar requests
Alerts - Be able to get alerts based on Frozen/Slow frame rates
0 votes · 0 comments
Alerts - I want to be able to get alerts based on the differences between releases
0 votes · 0 comments
Support webhooks for spike protection alerts so partners can build alerts for these too
15 votes · 0 comments
Alerts - Getting alerts on status change Ongoing -> Escalating
2 votes · 0 comments
Official JIRA integration should be available as a destination for *Metric* alert rules
0 votes · 0 comments
No comments yet.