Controlling data overhead from the OpenTelmetry Collector
summary
OpenTelemetry Collector configuration reduces telemetry volume and strips PII by running processors that drop debug logs, normalize variant keys into canonical labels, and lift path query values into attributes, using OTL and the filter processor / transform processor for complex rewrites. Collector is lightweight and deployable near edge services, which cuts latency, but remains stateless so it cannot join spans across long time windows or perform long-lived aggregation; use the tail sampling processor or external stateful systems for those needs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:26What is OpenTelemetry
- 5:23Why use the Collector
- 9:15Filtering theory and cardinality
- 13:03Separation of concerns
- 15:11OpenTelemetry Transform Language basics
- 17:42Filtering tips and tricks
- 20:11Collector processor limits
- 23:02Logging integration challenges
- 25:22Q&A
related talks
23mControlling Data Overhead with the OpenTelemetry Collector
01h 03mGet a Grip on your Telemetry using the OpenTelemetry Collector
13mManaging Observability Data at the Edge with the OpenTelemetry Collector and OTTL
16mUsing the OpenTelemetry Collector to Empower End Users
24mUnlocking Advanced Processing Capabilities with OpenTelemetry
26mDecoding OpenTelemetry(OTel) Collector: A Deep Dive into Architecture
25mOpenTelemetry Collector Deployment Patterns
16mDevs, Transform (Your Data) and Roll Out!: Learning and Leveraging OTTL