Loading content
An Error Budget Policy specifies how much unreliability a service may tolerate over a defined period and which organizational actions trigger on breach. It ties SLOs to release, prioritization, and incident-response rules. The policy makes risk measurable and embeds accountability into operational governance.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
An Error Budget Policy defines how much unreliability a service may tolerate over a period and which organizational decisions follow when that limit is exceeded.
The approach emerged in site reliability engineering, especially at Google, from the problem of making reliability actionable rather than merely measurable. In the SRE model, SLIs, SLOs, and error budgets connect measurement to decisions; the SRE book describes an error budget as an SLO for meeting other SLOs and as a signal for rollouts and priorities.
Think of the policy as a budget account: the SLO is the target, and every missed target spends credit. While credit remains, releases, experiments, and speed are still possible. When the account runs low or empty, attention shifts from velocity to stabilization, incident response, and root-cause work.
Formal rules define how decisions, exceptions, and responsibilities are handled across the organization.
Measurable reliability targets provide the reference point for acceptable failure.
The permitted share of missed targets within a defined time window.
The policy can slow or stop releases once the budget is exhausted.
Once budget is consumed, the focus shifts to containment, recovery, and follow-up work.
The policy is useful when teams need to balance releases against availability goals, prioritize reliability work, or agree on escalation rules. It only works with trustworthy SLIs and shared SLOs; otherwise the budget becomes a formal number with no steering effect. Too strict a policy can slow innovation, while too loose a policy may not protect users enough.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.