A peek into observability from testers lens
summary
Joiner finds a personal case study about moving from no visibility and many blocked tickets to a pragmatic rollout: start by shipping a proof‑of‑concept that centralizes logs, then add traces and metrics and incremental instrumentation. The claim is concrete: centralized structured logs replace SSH + Notepad++ chaos, traces show end‑to‑end requests, and small steps let the team debug faster and catch unknown unknowns. Practical focus on implementation and team change, not theory.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:30What is observability
- 10:35Visibility
- 11:00Observability
- 13:00Data
- 13:15Instrumentation
- 13:45Log
- 14:45Centralized logs
- 16:50Metrics
- 19:00Questions
- 23:25Exploration
- 26:55Finding unknown unknowns
- 27:40How to advocate for quality
- 31:15Conclusion
- 33:50Outro
related talks
21mPeek into Observability from testers lens
23mA peek into observability from a tester's lens
29mObservability for Developers: How to Get From Here to There
08m“Observability for testers”
31mObservability for Developers: How to Get There
53mObservability Driven Development
29mObservability; a gentle introduction
24mOperationalizing Observability: The Invisible Parts