Grafana Labs Customers: What We've Learned Building Observability at Massive Scale
summary
Hundreds of teams create fragmentation so the org consolidates around moved to Grafana Cloud to solve storage and scale, then builds a maturity model and observability guild to onboard power users. Outcome metrics focus on reduced MTTR and SLO-driven alerts; a surprise win is an S3-cost use case that saved money and a debug-log stream that consumed 25% of the logging cluster. Next steps are embedding observability left and exploring adaptive metrics and AIOps.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:29Defining observability
- 8:04Measuring observability beyond MTTR
- 12:46Scaling observability challenges
- 20:18Mistakes and lessons learned
- 27:59Observability team structure
- 33:04Observability and business outcomes
- 36:41Financial services regulations
- 40:00Cost pressures and metrics
- 42:35Future of observability & Q&A
related talks
26mAI-Driven Cloud Observability: Reduce toil and amplify time to resolution
32mEssential Software Observability for Every Role: Look No Further
31mCharting New Frontiers: The Evolution of Observability in Cloud Environments
23mImplementation of Unified Observability at Scale From Scratch
34mThe Grafana Stack: Building a Highly Available, Scalable Observability Platform
28mMonitoring Stack was yesterday – Observability Platform at scale!
13mLightning Talk: Observability-First DevSecOps: Building Resilient Multi-Cloud P...
12mOpen-source observability is the way forward, and here’s why