Getting Started with SRE
summary
Explains concrete SRE practices: define measurable SLOs with enforced error budget policy (example 99.9% → 0.1% = 43 minutes per month), treat an error budget as a spending limit that pauses risky releases and triggers remediation when exhausted, and prefer fixing root causes over hiring more on‑call. Recommends first SRE work: set/refine SLOs, shorten release size, add progressive deploys, automate toil (goal: cap toil so at least 50% time goes to project work). Gives a real case where a 6‑hour SLO cut paging and freed engineers.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:41What is SRE?
- 3:15The Site Reliablity Principles
- 7:55How Reliable Do You Want To Be?
- 8:38Error Budgets
- 10:54Error Budget Policy Examples
- 11:49SRE Principle #1
- 14:19Making Tomorrow Better Than Today
- 14:40Your First SRE
- 16:18Project Work
- 17:29SRE Principle #2
- 18:48Shared Responsibility
- 20:07Regulating Workload
- 21:06Leadership Buyin
- 23:08Reliability and Consistency Up Front
- 24:09Automation
- 24:46SRE Principle #3
related talks
47mSRE Team Lifecycles
22mSRE for Enterprises
38mImplementing SRE practices: SLI/SLO deep dive
31mSite Reliability Engineering (SRE) and...
30mImproving Reliability w/ Error Budgets & SRE
25mUnleashing the potential of SRE for modern operations
09mHow to answer tricky questions the SRE way
43mWhere SRE Can Go Wrong