Observability is Too Expensive!
summary
Claims that observability costs hit 10–30% of ops budgets and that 99% of indexed observability data is never searched and 30% of data is never used at all. Shows real audits where teams pay premium for dead dev servers, vendors lock customers with proprietary agents so migrations can take six months, while otel can switch in a few configuration lines. Recommends use‑case driven ingestion (hot storage for payment logs, S3 for debug), warns about overages and per‑feature per‑host charges that can multiply bills.
AI-written summary · about
chapters (9)
- 0:00Introduction and story
- 2:06Data growth and costs
- 5:11Challenges in observability costs
- 8:17Use case driven data pipeline
- 10:24Vendor lock-in risks
- 12:11Hidden pricing layers
- 15:48Fear and engineering empowerment
- 16:50Smart observability advice
- 17:55Q&A on cost management
related talks
27mObservability is Too Damn Expensive!
10mWhy your observability is costing you too much?
30mObservability is Too Expensive - Chris Cooney
35mDriving down the cost of observability
38mThe Ticking Time Bomb of Observability Expectations
52mObservability: it's not just an ops thing
36mObservability? It's a Data Analytics Problem, You Fool!
42mObservability Is Not Analytics!