Panel - Observability: What's the big idea?
summary
Observability is a superset of monitoring and focuses on detecting emergent behavior that developers cannot predict, not just prewritten alerts. Essential outputs are metrics events logs and traces consolidated across teams, with service level objectives to summarize reliability. Chaos experiments and testing in production are useful but run in staged, mirrored environments first. Rely on basic statistics, for example percentiles not averages, and budget people and money for the observability stack.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:30Alex Hidalgo
- 4:30Monitoring
- 6:10Observability vs Monitoring
- 10:40Observing Complex Systems
- 12:17Breaking Down Complex Systems
- 13:50Data Points for Complex Systems
- 16:20Testing in Production
- 18:55Chaos Engineering
- 20:20Observability
- 21:12Choosing a tool
- 22:47Understanding models
- 24:00Advice
- 25:48Math
- 26:30Outro
related talks
50mPanel: Observability
35mObservability: Building Confidence & Answering the What, Where, How
39mThe 5W’s of Observability with Practical Examples
42mObservability can help you understand change
29mObservability; a gentle introduction
30mObservability is More than Logs, Metrics & Traces
05mIgnite - Observability Observed
06mIgnite: Observability Observed