Observability Concepts Every Developer Should Know
summary
Summarizes three concrete developer takeaways: 3 core concepts — know telemetry types (logs, metrics, traces, events), map the telemetry journey (generators, collectors like Fluent Bit, exporters, storage) and learn to read/critique visualizations and queries (Prometheus/PromQL, OpenTelemetry sampling caveats). Calls out tool sprawl — organizations often run tool sprawl (5+ tools) and hidden processing that drops fields or routes infra vs app logs to different platforms. Recommends hands‑on fixes: cookbooks, short snippets, paired investigations and a production scavenger hunt to reduce bill and shift ownership.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:55Observability gaps for developers
- 10:21Three key observability concepts
- 17:50When to invest in learning
- 23:52Deciphering visualizations
- 30:59Next steps and resources
- 33:47Q&A and closing
related talks
29mObservability for Developers: How to Get From Here to There
33mWhat Developers Should Know About Observability
31mObservability for Developers: How to Get There
35mObservability: Building Confidence & Answering the What, Where, How
29mObservability; a gentle introduction
13mObservability that matters
26mYou Can’t Fix What You Can’t See: Tales from the Observability Frontier
35mBeyond Logs, Metrics and Traces. The Data Analytics Paradigm Shift in Observability — Dotan Horovits