How To Adopt OpenTelemetry in an Enterprise Where Incumbent Vendor Tools Reign Supre...
Talkat KubeCon + CloudNativeCon Europe 2025 · on Thursday, 2025-04-03· at 14:15· Level 1 | Hall Entrance N10 | Room G·
summary
Three-year enterprise rollout uses OpenTelemetry to cut MTTR dramatically — a production incident post-instrumentation goes from hours to under 15 minutes — by replacing many vendor silos with a narrowed backend catalog (goal: five or fewer) and centralizing pipelines. Changes include injecting OpenTelemetry via updated custom logging SDKs (covering 85–90% logging libraries), deploying the OpenTelemetry Collector at the edge, favoring auto-instrumentation, deferring metrics until SDKs stabilize, and adopting an embedded expert model to train app teams while keeping collector ownership with platform. Some backends are open source, some vendor hosted, and the approach proves effective.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:23The case for observability
- 8:14Strategy and tool selection
- 14:38Logging and implementation
- 18:57Traces and metrics rollout
- 22:08Collector and architecture
- 24:28Key lessons learned
- 27:00Enterprise-wide scaling
- 29:28Takeaways and Q&A
related talks
36mPanel: OpenTelemetry...
35mTales of Adopting OpenTelemetry: A First-Timer Journey
22mBridging the OpenTelemetry Adoption Gap in Cloud-Native Applications
34mPanel: OpenTelemetry: Bridging Platform and Enablement
20mObservability and Open Telemetry
28mFrom Legacy Vendor Tooling To OTEL: Scaling Observability at MSCI With a Four-Person Team
36mIncremental Strategies for Adopting OpenTelemetry
38mThe State of OpenTelemetry