Open Source for Better Observability
summary
Cloud native observability relies on concrete stacks: Prometheus + Grafana for metrics, Elasticsearch → OpenSearch (plus Kibana) or Loki for logs, and Jaeger (and Zipkin/Tempo) for traces. The field suffers tool sprawl—half use 5+ tools, a third use 10+—so correlating signals is hard. OpenTelemetry provides a unified API/SDK, an OpenTelemetry collector and OTLP to emit/route metrics, traces and logs to any backend. Structured logs, exemplars for metrics and trace correlation are practical fixes that actually enable answers.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:46Monitoring challenges
- 4:16Defining observability
- 7:21The three pillars
- 12:53Open source insights
- 18:28Leading open source tools
- 29:51Best practices
- 34:02Open telemetry overview
- 39:08Summary and conclusion
related talks
28mOpen Source for Better Observability
45mOpen Source for Better Observability
13mArchitecting an open observability stack
35mOpenTelemetry for Busy People
12mOpen-source observability is the way forward, and here’s why
50mOpen Telemetry: The Rise of Open Standards in Observability
22mBridging the OpenTelemetry Adoption Gap in Cloud-Native Applications
30mIs Building an Observability Platform with Open Source the Right Choice?