Using the OpenTelemetry Collector to Empower End Users
Talkat KubeCon + CloudNativeCon North America 2020 Virtual · on Thursday, 2020-11-19· at 13:01· Intrado Virtual Event Platform,·
summary
An executable pipeline called OpenTelemetry Collector receives metrics and traces via multiple protocols, converts them to an internal format, applies processors like the attribute processor to add missing fields or strip PII, and exports to one or many back ends. It runs as a sidecar or standalone, can merge Zipkin and Jaeger traces into one pipeline, does sampling, batching and memory limiting, and enables side‑by‑side backend comparison without changing application code.
AI-written summary · about
chapters (16)
- 0:00Thank You to Our Session Recording Sponsor
- 0:27What is Open Telemetry
- 1:20Why Open Telemetry Now?
- 2:43Another migration
- 3:18A path forward
- 4:17Deployment model
- 4:53Pipelines
- 5:30Complex operations
- 6:05Managing multiple flows
- 8:51Standardizing the data
- 9:42Enriching your data
- 11:27Forwarding that data along
- 13:05Easier* operations
- 13:36Takeaways
- 14:55My hopes for you...
- 15:19Run, don't walk
related talks
01h 03mGet a Grip on your Telemetry using the OpenTelemetry Collector
32mOpenTelemetry feat. logs, metrics and traces
23mControlling Data Overhead with the OpenTelemetry Collector
28mGetting Started with OpenTelemetry
28mControlling data overhead from the OpenTelmetry Collector
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
49mAdding OpenTelemetry to Production Apps Lessons Learned
13mManaging Observability Data at the Edge with the OpenTelemetry Collector and OTTL