SLO Error Budget Burn Analyzer
Track error budget burn rate and time to exhaustion. Enter values for instant results with step-by-step formulas.
Formula
BurnRate = CurrentErrorRate / AllowedErrorRate
The Burn Rate tells you how fast you are consuming your error budget relative to the target. A Burn Rate of 1 means you will exactly hit 0 budget at the end of the window. A Burn Rate of 10 means you will run out in 3 days (for a 30-day window).
Worked Examples
Example 1: Safe
Problem:SLO 99.9%, Current Errors 0.05%
Solution:Allowed 0.1%. Burning at 0.5x speed. Safe to ship.
Result:Burn Rate: 0.5x
Example 2: On Fire
Problem:SLO 99.9%, Current Errors 0.5%
Solution:Allowed 0.1%. Burning at 5x speed. Budget empty in 6 days.
Result:Burn Rate: 5.0x
Example 3: Depleted
Problem:Budget < 0
Solution:Code Freeze. Focus on reliability fix.
Result:Status: Freeze
Frequently Asked Questions
What is an Error Budget?
The allowed amount of unreliability. If SLO is 99.9%, your Error Budget is 0.1%. It represents the 'risk' you can spend on innovation.
What happens when budget is gone?
In strict SRE culture (Google model), you stop shipping new features (Code Freeze) and only work on reliability bugs until the budget replenishes.
Why use Burn Rate for alerts?
Alerting on raw error rate is noisy. Alerting on 'Burn Rate' predicts IF you will violate the SLO, reducing false positives for minor blips.
SLI vs SLO vs SLA?
SLI: The metric (Latency). SLO: The internal goal ( < 200ms). SLA: The contract with customer ($ penalty if missed).