Off the Beaten Path: Moving Observability Focus from Your Service
summary
Argues that observability must shift toward measurable customer experience and gives concrete techniques: use W3C Network Error Logging to expose survivorship bias (finding ISP routing mistakes), run large-scale session replay with clarity.js to see antivirus-injected ads and gray failures, apply Stanford CoreNLP for sentiment on in-the-moment feedback, and build insider programs and listening tours to surface issues numbers and context miss. Shows that focusing on distribution, not just high percentiles, reveals surprising targets for improvement.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:20Observability, for the next 20-30 minutes
- 4:53Observability Focus - A Shift
- 6:18Availability: Less Than What You Think It Is
- 8:05Network Error Logging
- 9:38Performance: More Than A Numbers Game
- 13:08How do you debug usability issues?
- 13:32What if you could see what your user saw?
- 13:53And, had the data to solve the usability issue
- 15:03Clarity-JS: Measure Usability @ Scale
- 16:03From Usability to Accessibility
- 18:28Ally Standards
- 23:32The Ugly
- 26:56A Good Feedback System Is....
- 29:06People Want To Be Cool Too
- 29:52Going Beyond Experimentation
- 30:46Isn't That Dogfood?
- 32:58Customer, Meet Engineer
- 34:19How Does It Help Engineering?
- 36:03The Feature You Work On Is 'The Site'
- 37:07Observability: The Collective Path
related talks
30mOff the Beaten Path: Moving Observability Focus from Your Service to Your Customer
31mNo-Nonsense Observability Improvement
29mObservability for Developers: How to Get From Here to There
39mObservability for Emerging Infra: What Got You Here Won't Get You There
29mObservability; a gentle introduction
53mObservable Web Applications
13mObservability Where are We Headed?
33mWhat Developers Should Know About Observability