Building a culture of observability
summary
Atlassian migrates monitoring to SignalFx over six months with five engineers, sending 1.5 million metrics/sec and onboarding over 2,000 developers and SREs. The team builds a single metric path and a metrics proxy with a blocklist, standardizes Terraform config, runs a monitoring bootcamp and platform auto‑dashboards and alerts, and cuts unused metrics roughly 50%. Migration uncovers aggregation errors, training proves essential, and the combined platform plus process changes materially reduce costs and improve visibility.
AI-written summary · about
chapters (23)
- 0:00Introduction to Session
- 1:08Defining Observability
- 2:03Observability vs Monitoring
- 4:12Telemetry Data Types
- 6:00Human Aspect of Ops
- 7:52Observability Culture
- 10:11Atlassian Case Study
- 12:34Streamlining Pipelines
- 15:06Developer Migration Strategy
- 17:22Lessons Learned in Migration
- 20:26Reducing Metric Usage
- 22:08Monitoring Bootcamps
- 24:06Proactive Operational Goals
- 25:57Internal Platform Tools
- 29:25Structuring Observability Teams
- 31:41Designing for Adoption
- 33:40Standardization and Support
- 35:57Marketing and Education
- 38:33Maintaining Engagement
- 41:03Data-Driven Decisions
- 43:33Continuous Improvement
- 46:11Measuring Success
- 50:01Conclusion
related talks
21mChallenges, Best Practices, and Solutions for Monitoring and Alerting...
51mHow to Successfully Manage a Technology Shift at a Global Scale
44mGrafana Labs Customers: What We've Learned Building Observability at Massive Scale
28mFrom Legacy Vendor Tooling To OTEL: Scaling Observability at MSCI With a Four-Person Team
28mMonitoring Stack was yesterday – Observability Platform at scale!
28mThings I wish I knew before we decided to migrate our metrics infrastructure..
44mIterative metrics, dashboards and monitors
37m5 reasons why (java) developers don’t buy in the observability hype