Mastering OpenTelemetry Collector Configuration
summary
Live demo shows an OpenTelemetry Collector YAML that actually runs: use the validate command to catch required fields before startup, start otelcol with a config that uses the debug exporter to print events, and watch host metrics appear on macOS (memory works, CPU/disk scrapers fail on macOS). Add processors memory_limiter and batch, set GO memory limits and a 450MB cap, and the pipeline handles tens of thousands of datapoints per second without crashing when configured correctly.
AI-written summary · about
chapters (10)
- 0:00Introduction and Icebreaker
- 0:17Challenges with YAML Configuration
- 0:34Introduction to OpenTelemetry
- 1:13OpenTelemetry Collector Overview
- 2:54Deployment Modes of OpenTelemetry Collector
- 5:58Configuring OpenTelemetry Collector
- 12:13Live Demo: Setting Up OpenTelemetry Collector
- 17:38Advanced Configuration and Production Tips
- 22:24Visualizing Configuration and Final Thoughts
- 25:26Q&A Session
related talks
01h 03mGet a Grip on your Telemetry using the OpenTelemetry Collector
23mControlling Data Overhead with the OpenTelemetry Collector
26mSimplifying OpenTelemetry with Configuration
16mUsing the OpenTelemetry Collector to Empower End Users
28mControlling data overhead from the OpenTelmetry Collector
31mTroubleshooting and Monitoring Production Applications using OpenTelemetry
25mOpenTelemetry Collector Deployment Patterns
25mDebugging the Pipeline: Observability for Your Observability with OTel + Prometheus