The 5W’s of Observability with Practical Examples
summary
Defines observability as data-driven debugging using structured events (wide key/value maps) and trace ID correlation to stitch logs, metrics and spans; recommends structured JSON logs, tracing as the glue, and using OpenTelemetry plus Grafana dashboards stored as code. Proposes an alert pyramid of actionable vs informational alerts, sidecar or eBPF collection for legacy services, pipeline-deployed dashboards, and automated governance (redaction rules and CI checks) to prevent log drift and secret leakage.
AI-written summary · about
chapters (7)
- 0:00Introduction to observability
- 7:27Why observability matters
- 13:46Building observable systems
- 23:03Key stakeholders in observability
- 26:36Left-shifting observability
- 35:27Governance in observability
- 38:41Summary and takeaways
related talks
35mObservability: Building Confidence & Answering the What, Where, How
30mObservability is More than Logs, Metrics & Traces
48mObservability or How to Know the State of Your System
29mObservability; a gentle introduction
42mObservability can help you understand change
36mObservability? It's a Data Analytics Problem, You Fool!
32mThe Role of Observability in Cloud Native Environments
35mBeyond Logs, Metrics and Traces. The Data Analytics Paradigm Shift in Observability — Dotan Horovits