Implement multiwindow multi-burn-rate SLO alerting for error budget management

domain: prometheus.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Define the SLO error rate and target availability as recording rules that compute the ratio of bad events to total events
  2. Calculate burn-rate as the ratio of the current error rate to the acceptable steady-state error rate derived from the SLO target
  3. Create a fast-burn alert using a short window (such as 1 hour) and high burn-rate threshold to catch sudden outages
  4. Create a slow-burn alert using a longer window (such as 6 hours or 3 days) and a lower burn-rate threshold to catch gradual degradation
  5. Require both the short and long windows to be above threshold simultaneously to reduce false positives from transient spikes

Known gotchas

Related routes

Implement SLO error budget burn rate alerting with multi-window alerts using Prometheus alerting rules
prometheus.io · 5 steps · unrated
Implement multi-window multi-burn-rate alerting for an SLO in Prometheus Alertmanager
prometheus.io · 6 steps · unrated
Implement multi-window multi-burn-rate SLO alerting in Prometheus following the Google SRE Workbook model
prometheus.io · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans