Opening the Door to Observability
summary
Argues that observability drives measurable business outcomes: marketing gains customer signals, leadership gets ROI-ready data, and security shifts from after‑the‑fact audits to continuous detection. Cites engineers juggling 15 different tools, replacement hiring costs of 50–80% of salary, Gartner’s prediction that 70% of cloud‑native apps will use open instrumentation by 2025, and the Atlassian incident that deleted sites for ~400 customers. Lays out a concrete plan: pick measurable objectives, compare open source and vendor options (OpenTelemetry supported), pilot one app, and report success criteria.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:13Observability for all
- 4:38Explain Observability
- 6:18Describe the Impact
- 12:46Build your Case
- 14:15Step 3.1: What's the objective? Is it one of these?
- 15:25Step 3.2: What are the Options?
- 19:04Step 3.3: Address concerns up-front
- 21:03Step 3.3: Build the Plan
- 24:17Step 3.5: Get buy-in
related talks
32mThe Role of Observability in Cloud Native Environments
24mOperationalizing Observability: The Invisible Parts
13mObservability that matters
29mObservability; a gentle introduction
07mKeynote: OpenTelemetry And The Future of Open Source Observability
01mObservability
45mOpen Source for Better Observability
33mKeynote: Observability is due for a version change; Are you ready for it?