SLOs with burn-rate alerts
Set an availability or latency objective on a service, watch its error budget, and get paged when the budget burns too fast.
You can now define service level objectives in Maple. An SLO covers one service’s incoming requests, optionally limited to some environments, and has:
- an SLI: availability (requests that did not fail) or latency (requests faster than a threshold from 50 ms to 10 s);
- a target, such as 99.9%;
- a rolling window of 7, 28 or 30 days.
Each SLO alerts on how fast it spends its error budget, not on single spikes. A critical page fires when the budget burns at 14.4 times the sustainable rate over both the last hour and the last 5 minutes. A warning fires at 6 times over both the last 6 hours and 30 minutes. A brief blip does not page, and the page clears as soon as the burn stops. The notification says which windows are burning and how fast. A gap in incoming data holds the alert where it is instead of resolving it.
Find SLOs under Alerts → SLOs. Each SLO’s page shows the SLI against the target, the budget
left, the budget over time, the burn rate of each window, and its incidents. SLOs are also
available from the /v2/slos API and MCP.