SRE Team Lifecycles
summary
Argues SRE is a lifecycle built on three concrete rules: set measurable SLOs and attach an error budget policy, give SREs bounded operational time so they have time for project work, and let teams regulate load by choosing which services to own. Uses specifics: 99.9% SLO = 43 minutes/month, Google finds ~70% of outages trace to config or binary changes, and a practical policy example is an error budget push freeze that decouples releases and reduced outages.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:55Who am I?
- 1:49What Do We Want From Site Reliability Engineering?
- 2:34You Already Do Site Reliability Engineering
- 4:17The Site Reliability Principles
- 5:42What is an SLO?
- 6:12Typical SLOS
- 7:23Alerting on SLOS
- 9:31How Reliable Do You Want To Be?
- 10:27Error Budgets
- 13:23Error Budget Policy Examples
- 16:17SRE Principle #1
- 19:24SRE Needs To Do Some Toil
- 20:24Project Work
- 22:35SRE Principle #2
- 25:21Shared Responsibility
- 27:40Regulating Workload
- 31:06Leadership Buy-in
- 33:25Reliability and consistency Up Front
- 34:24Automation
- 35:37SRE Principle #3
