Stage 1 · Lesson 5 of 6
Error budget policies
An only changes behaviour if everyone agrees in advance what happens when it runs low. An is a short document, agreed by engineering and product leadership, that says so. A typical policy: if the service has used its budget over the window, non-urgent releases pause and the team works on reliability until it recovers; if one uses more than a fifth of the budget, it gets a with priority action items.
It also names exceptions, such as security fixes, and who can override. The value is that the decision is made calmly, not argued during an outage.
Common trapwriting a policy that only the SRE team signed, which is ignored the first time a launch date is at stake.
A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock
Resources for this stage
Start with· follow one of these
- BookFreeGoogle Site Reliability Engineering Book
Google · Advanced
Free online: read the chapters on embracing risk and service level objectives first
- BookFreeThe Site Reliability Workbook
Google (O'Reilly) · Intermediate
Free online: the Implementing SLOs chapter walks through a worked example and an error budget policy