SRE
Site reliability engineering: Google's approach of running operations as a software engineering problem, with reliability targets, error budgets and limits on toil.
In more detail
SRE supplies the vocabulary of service level indicators, objectives and agreements, error budgets, on-call, toil and blameless postmortems. The Google SRE book and workbook are its primary sources.
Related terms
- Site Reliability Engineering book — The book in which Google engineers describe how they run production systems, free to read online, with an appendix example postmortem.
- service level objective — A target for a service level indicator over a time window, such as 99.9 per cent of checkouts succeeding over 30 days.
- error budget — The amount of failure an SLO allows over its window: one minus the target, for example 0.1 per cent of requests at 99.9 per cent.
- toil — Manual, repetitive, automatable operational work that grows with the service and leaves no lasting value.
Taught in
- What DevOps Actually Is — DevOps & Site Reliability Engineering
- Service Level Objectives — DevOps & Site Reliability Engineering
- Service Level Agreements: The Consequence Discriminator — DevOps & Site Reliability Engineering
- Error Budgets — DevOps & Site Reliability Engineering
- The Blameless Postmortem — DevOps & Site Reliability Engineering
- Writing A Postmortem: The SRE Appendix — DevOps & Site Reliability Engineering
- Who Decides What Ships: The CNCF And Its Community — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Ninety Nine Percent Of What? SLIs, SLOs And SLAs — Prometheus Certified Associate (PCA) Exam Prep
- Observability Sprint: One Failed Checkout — Prometheus Certified Associate (PCA) Exam Prep