Essential Software Observability for Every Role: Look No Further
summary
Argues that observability is about detecting unexpected change, not nicer dashboards, citing 18 deploys per day and the ladder from basic monitoring → faster debugging → impact analysis → proactive actions to improved uptime. Calls out buy vs build tradeoffs: high TCO, vendor lock‑in and high cardinality when buying, nine months to a year of toil and poor adoption when building with Grafana/Elasticsearch. Proposes CoroLogix hybrid solution to combine benefits, recommends SLOs and service cataloging as practical next steps.
AI-written summary · about
chapters (17)
- 0:00Introduction to Software Observability
- 0:11The Importance of Observability
- 1:39Impact of Changes in Software
- 2:58Types of Changes in Systems
- 4:32The Need for Continuous Monitoring
- 7:27Roles in Observability
- 8:36Stages of Observability
- 9:35Key Questions in Observability
- 14:46Building or Buying Observability Systems
- 15:15Balancing Build vs. Buy Decisions
- 16:12Challenges of Buying Observability Software
- 17:36Pitfalls of Building Your Own Solution
- 19:11Introducing CoroLogix: A Hybrid Solution
- 19:31The Importance of Software Observability
- 20:30Open Source Alternatives and Building Solutions
- 21:40Q&A Session: Addressing Audience Concerns
- 29:38Future Trends in Observability
related talks
40mDemystifying Observability and Monitoring
32mThe Role of Observability in Cloud Native Environments
12mOpen-source observability is the way forward, and here’s why
31mCharting New Frontiers: The Evolution of Observability in Cloud Environments
30mIs Building an Observability Platform with Open Source the Right Choice?
29mObservability for Developers: How to Get From Here to There
44mGrafana Labs Customers: What We've Learned Building Observability at Massive Scale
46mObservability engineer, the best friend you never knew you had