One Binary, Two Ecosystems: Embedding Prometheus Exporters With OCB
summary
Shows a working bridge that embeds existing Prometheus exporters directly into a custom OpenTelemetry Collector built with OCB, removing the HTTP scrape hop and running exporter code in memory via a provided Prometheus registry. Demonstration compiles a collector including the Postgres exporter from a PR commit and collects the same metrics (Postgres exporter exposes ~500 metrics versus the OSS OT receiver’s ~20). Covers using OTTL transforms for semantic convention mapping and the refactor work needed to make exporters embeddable.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:19Prometheus exporters
- 4:28OpenTelemetry collector overview
- 6:38Challenges with contrib
- 7:59Introducing OpenTelemetry Collector Builder
- 9:07Prometheus vs OpenTelemetry
- 12:48Bridging exporters with OTel
- 13:52Demo setup and PostgreSQL exporter
- 16:14Embedding exporters in OTel
- 19:07Demo results and metrics
- 20:10Semantic conventions
- 22:55Challenges and future
- 24:00How to contribute
- 25:25Summary and call to action
- 26:52Q&A
related talks
24mCustomize Your Own OpenTelemetry Collector: An Introduction To OCB
26mDecoding OpenTelemetry(OTel) Collector: A Deep Dive into Architecture
37mShould I Use OTel (collectors), or Is Prometheus Good Enough?
25mDebugging the Pipeline: Observability for Your Observability with OTel + Prometheus
36mShould I use OTel (collectors), or is Prometheus good enough?
22mBuilding Prometheus Metrics Support in OpenTelemetry
24mLeveraging OpenTelemetry for Your Prometheus Pipeline
37mObservability For You And Me With Opentelemetry