Understanding Error Budget Burn Rate
How we calculate. Burn rate = (error budget consumed %) ÷ (percent of SLO period elapsed). The form uses the same arithmetic as the worked examples on this page. See our methodology and accuracy policy.
Real-world scenario: A typical Error Budget Burn Rate case uses error budget consumed (%) 40 and period elapsed (%) 20. Enter the same figures below to reproduce the worked path.
What is Error Budget Burn Rate?
A classic SRE multi-window alerting signal. Burn rate 1 means you are on track to exhaust the budget exactly at period end; above 1 means overspending.
- Consumed % from your SLO math
- Elapsed % = time passed ÷ period × 100
- Alert on sustained high burn
The Formula
Worked Example
Common Use Cases
- Page policies: multi-window burn alerts
- Incident response: stop the bleed
- SLO coaching: early-month risk
Pro Tips
- Use short and long windows together
- Recalculate after major incidents
- Pair with remaining %
Limitations: Error Budget Burn Rate results are educational DevOps/SRE/FinOps planning aids—not SLAs, billing guarantees, or operational policy. Confirm definitions with your platform and finance teams.
FAQ
What does burn rate 1 mean?
You are consuming budget at a pace that would hit 100% consumed exactly at period end—if the rate continues.
What if period elapsed is 0?
Burn rate is undefined—wait until some of the window has elapsed.
Authoritative References
For SRE and FinOps definitions, consult:
- Google SRE books — SLOs, error budgets, toil
- DORA — delivery performance research
- FinOps Foundation — cloud cost practices