Should I Use OTel (collectors), or Is Prometheus Good Enough?
summary
Replaces homegrown scraping agents with an OTel collector cluster that runs alongside workloads and a dedicated management cluster, enabling exporting to Datadog, Tempo, or any OTLP backend without changing app code; uses the prometheus receiver to ingest Prom metrics but notes scaling and feature gaps (alerts, high‑cardinality queries) and the need for a phased migration, rollback plan, and testing; Solo.io migration works and simplifies integrations.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:20What is OpenTelemetry
- 12:52Traditional observability tools
- 14:19OpenTelemetry collectors simplify vendor integration
- 17:10Switching from Prometheus to OpenTelemetry collectors
- 25:17Migrating vendor agents to OpenTelemetry collectors
- 29:31Scalable telemetry pipelines with OpenTelemetry
- 34:48Key takeaways and final recommendations
related talks
36mShould I use OTel (collectors), or is Prometheus good enough?
24mLeveraging OpenTelemetry for Your Prometheus Pipeline
11mLightning Talk: OTel Me How to Build a Data Pipeline for Observability
25mDebugging the Pipeline: Observability for Your Observability with OTel + Prometheus
31mEvolving Prometheus for More Use Cases
22mBuilding Prometheus Metrics Support in OpenTelemetry
31mOne Binary, Two Ecosystems: Embedding Prometheus Exporters With OCB
10mUpstream-First, High Scale Prometheus Ecosystem