Start here
Error budgets: calculate the allowance and agree how to use it
Connect the objective, measurement window and eligible population.
Read the articleSLOs & reliability
Connect service objectives to error budgets, alerting and release decisions.
Work through the calculation
Error-budget template: calculations and release-policy fields
Use the calculation examples and policy fields for a service record.
Read the guideAgree on the decision
Error-budget policy: agree on the decision before the outage
Define the release policy before an incident puts it under pressure.
Read the articleReview the release gate
Release gates that hold up under incident pressure
Connect policy thresholds to an owned operational decision.
Read the guidePut it into practice
Calculator
Error-budget calculator
Calculate the allowed bad events and remaining budget for a measurement period.
- Input
- An SLO and eligible event or time totals
- Output
- Allowed, consumed and remaining budget in the chosen units
Calculator
SLO burn-rate calculator
Estimate budget consumption at an observed error rate, with explicit assumptions.
- Input
- An SLO and counts for two nested windows
- Output
- Two-window burn rates with threshold and scope checks
More on slos & reliability
Guide · 7 min read
Prometheus missing data: test what your error-rate alert cannot see
A zero fallback can hide missing telemetry. Use a small PromQL test matrix to check what your error-rate alert can and cannot establish.
Guide · 7 min read
Kubernetes disruption budgets: test the capacity left behind
Plan an inference-service node drain with a scoped disruption budget, replacement-capacity checks and a practical maintenance worksheet.
Guide · 4 min read
Canary deployments: limit exposure and test the comparison
Choose representative traffic, define promotion criteria, and verify rollback compatibility before expanding a release.
Explainer · 3 min read
Service level objectives: define the experience you intend to protect
Choose an SLI, target, and evaluation window that reflect user experience, then agree on the decisions an SLO result will change.