Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Create a new metric alert.
- In Set issue detection thresholds, choose Percent Change (e.g., compared to same time one week ago).
- Critical:
90 / Lower than.
- Warning:
75 / Lower than.
- Resolved:
0 (or any value lower than Critical).
- Click save.
Expected Result
The alert saves.
Use case: fire when a metric (e.g., throughput) is 90% or more lower than the comparison period, and resolve once the metric has recovered.
In Percent Change + Lower than, a larger percentage represents a more severe drop:
90% lower → most severe75% lower → less severe0% → fully recovered
So Resolved 0% is the correct "recovered" state and is lower in severity than Critical 90%.
Actual Result
Save is blocked by a validation error on both Critical and Warning:
Alert threshold must be less than resolution
The form appears to require the Resolved threshold to be greater than Critical, which for a "Lower than" percent-change alert would mean "resolve only when the drop gets worse."
For reference, the Warning-vs-Critical check in the same form accepts Warning 75 < Critical 90 without issue, only the Resolved check seems to be the blocker.
Product Area
Alerts
Link
No response
DSN
No response
Version
No response
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
90/ Lower than.75/ Lower than.0(or any value lower than Critical).Expected Result
The alert saves.
Use case: fire when a metric (e.g., throughput) is 90% or more lower than the comparison period, and resolve once the metric has recovered.
In Percent Change + Lower than, a larger percentage represents a more severe drop:
90%lower → most severe75%lower → less severe0%→ fully recoveredSo Resolved
0%is the correct "recovered" state and is lower in severity than Critical90%.Actual Result
Save is blocked by a validation error on both Critical and Warning:
The form appears to require the Resolved threshold to be greater than Critical, which for a "Lower than" percent-change alert would mean "resolve only when the drop gets worse."
For reference, the Warning-vs-Critical check in the same form accepts Warning
75< Critical90without issue, only the Resolved check seems to be the blocker.Product Area
Alerts
Link
No response
DSN
No response
Version
No response