Where to start with Google’s free SRE books
A chapter-level starting point for alerting, on-call coverage and postmortems, with examples of adapting the practices to local staffing and authority.
Reliability engineering, from service objectives to operational judgment.
A chapter-level starting point for alerting, on-call coverage and postmortems, with examples of adapting the practices to local staffing and authority.
Traffic assignment determines which behavior reaches a canary. Promotion also depends on the baseline, service objectives and state left behind by rollback.
Worked incident records explain the MTTD formula, uncertain onset times and the effect of including failures first reported by customers.
A mistaken target selection shows how an incident review can explain a responder’s choice and lead to a more useful interface improvement.
A delayed rollback connects the incident timeline to the information responders had, the compatibility question they faced and the follow-up that remains.
Feature flags and customer overrides show why a shorter configuration file can leave just as much behavior to investigate and support.
Counters, gauges and distributions preserve different information. A misleading latency trend shows why the counted requests matter as much as the chart.
An unfinished worker operation connects event fields, collection loss and search permissions to the responder’s next retry decision.
Primary shifts, specialist help, absence coverage and recovery time all contribute to the service an on-call calendar promises.
A downloadable Markdown template and a worked database-connection investigation show how observations lead to mitigation and recovery checks.
Images package processes and Kubernetes reconciles their deployment. Probes, resource settings and completed jobs reveal different stages of the service.
A backup-failure alert illustrates the gap between shipping a postmortem action and giving its recipient the access needed to respond.