Managing Observability Data at the Edge with the OpenTelemetry Collector and OTTL
summary
OpenTelemetry Collector deploys to sidecars to parse JSON logs, filter debug-level noise, and redact PII by replacing purchase IDs with a sha256 hash stored temporarily in OTTL cache; a central collector uses the routing connector to send anything starting with "retail" to the old backend and everything else to the companywide pipeline, which applies tail sampling driven by OTTL rules: sample all errors, all payment-service traces, or roughly 1-in-16 traces by checking if hex trace ID starts with "a". Config demo works but is not production-ready and the project adds about 15 new functions this year.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:48What is The Collector
- 2:30Case Study
- 3:40Filter Processing
- 4:56Log Processing
- 7:00Routing
- 8:48Resting config
- 9:20New features
- 10:05Looking ahead
- 10:30Dock links
- 10:45Questions
related talks
28mControlling data overhead from the OpenTelmetry Collector
50mGuide to Observability with OpenTelemetry
37mObservability For You And Me With Opentelemetry
01h 03mGet a Grip on your Telemetry using the OpenTelemetry Collector
36mObservability For You and Me with OpenTelemetry
16mDevs, Transform (Your Data) and Roll Out!: Learning and Leveraging OTTL
18mOpenTelemetry and Observability: What, Why, and Why Now?
01h 03mOpenTelemetry in a Brownfield World