Fueling system discovery with observability
summary
Observability reframes monitoring by collecting wide structured events that keep full context so engineers can derive metrics from events rather than the reverse, and unify those events with traces to zoom from a waterfall visualization to affected cohorts. Modern distributed systems produce rare intersections of failures — like one in a billion events — so ownership requires the same engineer to write, deploy, roll back and debug in production. Invest in deploy tooling, guardrails and observability from commit to decommission; DORA-style velocity reduces errors.
AI-written summary · about
chapters (5)
related talks
35mObservability: Building Confidence & Answering the What, Where, How
42mObservability can help you understand change
52mObservability: it's not just an ops thing
40mDemystifying Observability and Monitoring
06mIgnite: Observability Observed
44mObservability for Emerging Infra: What Got You Here Won’t Get You There
46mObservability for Emerging Infra: What Got You Here Won't Get You There
30mObservability is More than Logs, Metrics & Traces