The More You Know: A Guide to Understanding your Systems
summary
A reusable template codifies three concrete sections — service context, pregame checklist, game day — so teams answer what the service does, who the customer is, and which SLI/SLOs measure real user experience. Teams run happy‑path load with Locust/Gatling, observe Datadog dashboards, optionally inject faults with Gremlin, and exercise incident playbooks and PagerDuty routing. Outcomes are specific: missing SLIs, noisy alerts, unclear runbooks get logged as backlog betterments, juniors gain operator muscle memory, and repeated runs validate fixes.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:23Why Understand Your Systems
- 1:03The Story
- 4:02The Challenge
- 4:55The Template
- 6:52The Toolbox
- 8:17The Game Day
- 9:30Expectations
- 11:22Learnings
- 14:33Thank You
- 14:45Where can we find this template
- 16:09How do you ensure that your most junior employee can answer questions
- 17:30Do you think that the format for that pairing of the med senior to the junior engineer should be in a game day format
- 18:38Operator mindset
- 20:29How people write code
- 22:32Muscle memory
related talks
38mBuilding Service Ownership Using Documentation, Telemetry, and a Chance to Make
31mNo-Nonsense Observability Improvement
19mLeveraging Analytics for Technical Efficiency and Enhanced User Experience
15mSustainable Incident Management for happy SRE teams
21mLive Q&A Session #1
46mObservability in the real world: Improve systems w/iterative approach
16mNavigating the What, Where, and When of Your Frontend App
40mFuzzy Lines: Aligning Teams to Monitor Your Application Ecosystem