Seeing Through the Chaos of Modern Systems
summary
Claims that OpenTelemetry standardizes telemetry and that an OpenTelemetry Collector centralizes receivers processors and exporters and reduces resource use. Gives concrete guidance: when to use push vs scrape (short‑lived or restricted networks vs Kubernetes/dynamic environments), tradeoffs of auto instrumentation (quick start, low effort) versus manual (precise business metrics), and plumbing examples using StatsD, Prometheus, Loki, Tempo, Mimir and Graphana plus Fluentd/Fluent Bit to aggregate logs and metrics.
AI-written summary · about
chapters (10)
- 0:00Introduction and Speaker Background
- 0:50Agenda Overview
- 1:35Foundations of Observability
- 3:01Telemetry Data Types and Collection Methods
- 10:49Introduction to Open Telemetry
- 11:46Open Telemetry Architecture
- 13:51Collector Components and Data Sources
- 17:27Implementation Approaches
- 18:35Full Observability Stack
- 21:52Conclusion and Thank You
related talks
43mWhat is this OpenTelemetry thing?
47mWhat Is This OpenTelemetry Thing?
34mKubernetes Observability with OpenTelemetry
15mOpenTelemetry: The Vision, the Reality and How To Get Started
35mOpenTelemetry for Busy People
50mOpen Telemetry: The Rise of Open Standards in Observability
19mOpenTelemetry's Path to Observability's Future
12mHarnessing Chaos Engineering to Build Robust Systems