SYS-1072
SLO slo is burning its error budget fast (burnRatex)
Why it happens
Over the last window, enough requests failed or were late to burn the slo error budget at burnRate times the allowed rate. At this rate the month's budget is gone within hours, and customers notice.
What to do
The Rabt on-call engineer must open an incident now following the incident response runbook, check the errors and traces of this SLO, and post the first customer update within 15 minutes.
- HTTP status
- 500
- Retrying does not help
- Placeholders
- sloburnRatewindow