SLO Error Budget Burn Rate Monitor

Convert real-time incident data into the burn multiplier Google SRE playbooks use. Compare observed error rate against the total budget to know when to trigger multi-window alerts or freeze deploys.

Availability or success SLO expressed as a percentage.
Length of the current measurement window.
Total number of failed requests or minutes of downtime observed.
Successful + failed events measured during the window.
Optional. Defaults to 720 hours (30 days).

Examples

  • SLO 99.9%, 1-hour window, 50 errors out of 3,000,000 requests, 30-day budget ⇒ burn rate 12.00×
  • SLO 99.5%, 6-hour window, 177 errors out of 2,500,000 requests, default budget ⇒ burn rate 1.70×

FAQ

How should I pick alert thresholds?

Common practice is to alert at 2× for short windows and 1× for longer windows so you can intervene before the budget is exhausted.

What if I track multiple SLOs?

Evaluate each service or objective separately, then prioritise remediation on the highest burn rates before they cascade.

Does this account for error budget resets?

Yes. Set the SLO budget window to your reset interval—weekly, monthly, or quarterly—to align with how you roll over remaining budget.

Additional Information

  • Burn rate compares observed error consumption to the pace permitted by the SLO window.
  • A value above 1 indicates the budget is depleting faster than allowed and should trigger alerts at predefined thresholds.
  • You can input downtime minutes instead of error counts if requests represent time-based objectives.

Related calculators