Where SRE leadership changes the reliability plan
SRE leaders resolve collisions between reliability work and delivery commitments, remove response obstacles and decide what the team can actually fund.
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.
SRE leaders resolve collisions between reliability work and delivery commitments, remove response obstacles and decide what the team can actually fund.
A deployment and a simultaneous dependency outage illustrate how AI-assisted observability can locate useful evidence and distinguish competing explanations.
Baselines, event-level precision and recall, and the cost of waiting determine whether an unusual pattern belongs in investigation or paging.
Choose what to instrument across a request, queue and worker, then check whether the resulting trace explains the wait.
Build a transparent keyword router, then learn what changes when a trained classifier chooses the destination.
Observation, collection and evaluation timestamps explain why the last zero-error result may no longer describe the service.
A queued upload illustrates the choice of SLI, target and window, including why endpoint success can miss the user’s unfinished task.
Concurrent spans, retries and selected samples explain what a trace reveals about one request and where an investigation needs another observation.
Alert cleanup can reduce interruption or conceal a recurring failure. Customer reports and correction effort help distinguish the two results.
Worked request and time examples explain error-budget units, remaining allowance and burn rate, plus the release policy that gives them a practical role.
Worked formulas and a scorecard connect customer outcomes, response delays and specialist workload to reliability investment.
A chapter-level starting point for alerting, on-call coverage and postmortems, with examples of adapting the practices to local staffing and authority.