OpenTelemetry and Epsagon - a Love Story in Three Acts
summary
Starts with closed-source SDKs and a proprietary trace format that customers refuse to install, moves to open libs then forked distributions of OpenTelemetry (fast to ship but costly to maintain), then switches to extending upstream via a Java agent distribution so onboarding is zero‑code and backend accepts OTLP. After acquisition the product line supports OpenTelemetry natively, contributors upstream, and an open‑source Jaeger‑replacement for visualizing traces is planned.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:38Overview
- 2:37Observability
- 6:19Challenges
- 11:05Distributed Traces
- 13:24The Epsilon Journey
- 19:57standardization of the market
- 26:24lesson 1 folks
- 27:17lesson 2 balance
- 28:02OpenTelemetry distribution
- 30:01Cisco acquisition
- 30:51Upcoming products
- 31:48Future of OpenTelemetry
- 32:25Outro
related talks
14mOpenTelemetry and Epsagon - A Love Story In Three Acts
32mOpenTelemetry feat. logs, metrics and traces
01h 08mOpenTelemetry: The First Release, What’s Next, and How to Get Involved
41mNavigating the Open Source Observability Landscape
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
15mOpenTelemetry: The Vision, the Reality and How To Get Started
34mOpenTelemetry: The Vision, Reality, and How to Get Started
30mOpenTelemetry 101