Ask a Site Reliability Engineer (SRE)
summary
Panel explains how Datadog builds SRE in practice: a five-person web reliability team grows into four or five API platform teams, they build an in‑house API framework that is half framework half SRE layer, run chaos engineering with a Kubernetes chaos controller and regular game days, and publish a weekly API reliability report from a Datadog notebook showing the top slowest and highest‑error endpoints to force prioritization. Emphasizes embedding SREs with measurable goals, automating any repeatable work (no manual bash scripts), and skepticism about adopting error budgets wholesale.
AI-written summary · about
chapters (13)
- 0:00Introductions and origins
- 1:40Defining DevOps culture
- 4:57The impact of version control
- 8:01Understanding SRE principles
- 10:44Scale and startup context
- 12:22Practical SRE implementation
- 15:25Embedded SRE models
- 19:11The role of platforms
- 22:05Audience Q&A: Team dynamics
- 27:47Audience Q&A: SRE anti-patterns
- 30:13Audience Q&A: Future of tools
- 33:19Audience Q&A: Evangelization
- 35:26Audience Q&A: Accountability
related talks
42mDemystifying SRE and DevOps
42mDemystifying SRE and DevOps
05mHow do Devops and SRE relate?
21mDO, RE, Me: Measuring the Effectiveness of Site Reliability Engineering
41mSRE in Enterprise
25mSRE in the Third Age
49mSite Reliability Engineering and the Security Team They Love
27mMean Time To SRE: A DevOps story from adidas
