The shoemaker’s children have no shoes - why SRE teams must help themselves
summary
Shows how an SRE team fixes a neglected internal CI environment called testbox by adding metrics and traces (a simple testbox tracing via log_event approach), discovers a 27% availability problem, locates a race condition, and ships a three-line fix. Builds a continuous synthetic prober customer-journey to surface regressions, iterates SLOs to avoid noisy paging, and uses postmortems and follow-up tickets to force prioritization. Practical tooling and numbers drive decisions, and the fixes measurably reduce developer friction.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:25The shoemakers children have no shoes
- 0:50What is an internal service
- 1:54What is SRE treatment
- 3:12Production
- 3:41Developer Experience
- 4:41Internal Services
- 6:57Customer Facing Services
- 8:55Testbox
- 10:16Slack
- 11:10Metrics
- 13:06Tracing
- 14:10spans
- 15:00logs
- 15:48interviews
- 17:55SRV Principles
- 18:15Classic SLI issue
- 21:16SLO
- 22:19Sr Brain
related talks
26mIncreasing the collaboration between SREs and Developers
43mWhere SRE Can Go Wrong
36mThinking like a site reliability engineer to improve CI
30mHow Did Things Go Right? Learning More from Incidents
34mThe Enterprise SRE (eSRE) Approach
22mSRE and Risk management: a love story
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
28mHow to Do SRE When You Have No SRE