3 Pitfalls Everyone Should Avoid with Cloud Data
summary
Three concrete pitfalls emerge: observability becomes data and costs explode — an example produces half a terabyte in 30 days from one test app and some customers ingest 380,000 points where dashboards need only 30 to 300. Tool sprawl averages 10 observability tools, storage policies keep data store data 13 months by default, and a news site shows cloud egress surges that would have bankrupted the business. Always plan an exit strategy and measure ingestion before sending it to storage.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:50Cloud costs at scale
- 8:41Observability cost trap
- 17:35FinOps for waste
- 21:54Key takeaways
- 25:45Q&A
related talks
10mWhy your observability is costing you too much?
38mThe Ticking Time Bomb of Observability Expectations
27mObservability is Too Damn Expensive!
22mObservability is Too Expensive!
25mThe History of DevOps in 30 minutes
30mBut Wait! There's...Still More‽ - Observability Data Volumes and Strategies for Managing Them
30mObservability is Too Expensive - Chris Cooney
31mLeveraging Data Output for Architectural Optimization