OpenTelemetry and Epsagon - A Love Story In Three Acts
summary
Epsagon chronicles moving from proprietary SDKs to OpenTelemetry adoption: building closed automatic instrumentation then open sourcing it, creating many forks of OpenTelemetry that become a maintenance burden, accruing tech debt while expanding from serverless to Kubernetes, then proving a java agent built as a distribution on top of OpenTelemetry works and lets Epsagon ingest OT traces, joining the OpenTelemetry community, contributing code, and ending with Epsagon acquired by Cisco. Forks are hard to maintain and open source distribution beats forking.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:28From SDKs to OpenTelemetry
- 3:55OpenTracing challenges
- 5:59Open source lessons
- 6:21Kubernetes and OpenTelemetry
- 8:29Forking OpenTelemetry pitfalls
- 9:55Joining OpenTelemetry
- 11:44Cisco acquisition plans
- 13:29OpenTelemetry contributions
related talks
34mOpenTelemetry and Epsagon - a Love Story in Three Acts
41mNavigating the Open Source Observability Landscape
01h 28mUnderstanding Distributed Systems with OpenTelemetry
18mOpenTelemetry and Observability: What, Why, and Why Now?
50mOpen Source Instrumentation - The Rise of OpenTelemetry
35mOpenTelemetry for Busy People
15mOpenTelemetry: The Vision, the Reality and How To Get Started
21mOpen Telemetry