From a postmortem finding to a working improvement
A backup-failure alert illustrates the gap between shipping a postmortem action and giving its recipient the access needed to respond.
Guides, news and explanations about AI and reliable systems.
Not sure where to begin? Choose a short reading path, or browse at your own pace.
A backup-failure alert illustrates the gap between shipping a postmortem action and giving its recipient the access needed to respond.
Time away depends on the work having somewhere else to go. Test the backup’s access, authority and capacity before the specialist leaves.
After an interrupted night, relief needs coverage and changed commitments. Then repair the recurring demand, including work that arrives outside the rota.
SRE leaders resolve collisions between reliability work and delivery commitments, remove response obstacles and decide what the team can actually fund.
An unusual pattern can deserve investigation without deserving a page. Define its expected behavior, count real events and choose a response that fits the consequence.
A refreshing page can repeat an old healthy result. Follow event, collection, evaluation and delivery times to find where current evidence stopped arriving.
A queued upload illustrates the choice of SLI, target and window, including why endpoint success can miss the user’s unfinished task.
A lower page count can hide the same failures arriving through support. Check the intended customer and responder result after changing the rule.
Worked request and time examples explain error-budget units, remaining allowance and burn rate, plus the release policy that gives them a practical role.
A chapter-level starting point for alerting, on-call coverage and postmortems, with examples of adapting the practices to local staffing and authority.