The Role of Observability in Cloud Native Environments
summary
Argues observability as the ability to answer unknown questions using telemetry and contrasts it with dashboard monitoring, lists concrete signals: logs, metrics, traces, profiles, events, and cites tools and projects like OpenTelemetry Collector, Prometheus, Jaeger, Grafana Labs, OCB and an operator; explains SLOs and error budgets as operational controls, gives a real tracing win that proved which microservice was slow and shifted a team from blame to fixing, and stresses 2 a.m. incident workflows.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:29Need for observability
- 7:57Agile to microservices
- 10:06DevOps and reliability
- 16:49Observability vs monitoring
- 21:46Cloud native observability needs
- 25:44Answering questions at 2 a.m. with observability
- 26:26Q&A
- 29:40Monitoring vs observability
- 31:05Event standards in observability
related talks
31mCloud Native Observability
28mOpen Source for Better Observability
31mCharting New Frontiers: The Evolution of Observability in Cloud Environments
29mObservability; a gentle introduction
16mBuilding Observability into Cloud-Native Applications
42mOpen Source for Better Observability
26mBeyond Monitoring: Empowering Observability in the Cloud-Native Era
35mObservability: Building Confidence & Answering the What, Where, How