Panel: OpenTelemetry...
summary
Companies migrate to OpenTelemetry to stop vendor lockin, correlate traces logs and metrics, and simplify bespoke pipelines; deployments favor a central gateway collector over sidecars to avoid credential and scaling pain. Migrations happen under the hood (OpenTracing shim) and roll out slowly per team, with audits for cardinality, dashboards to show per-team telemetry cost, and rule-based dropping or tailed sampling to limit volume. Adoption leans on a common semantic conventions model and platform enablement plus observability champions.
AI-written summary · about
chapters (6)
- 0:00Welcome
- 1:47Why adopt OpenTelemetry
- 9:34Rolling out OpenTelemetry
- 15:33Adopting Open Standards
- 22:17OpenTelemetry challenges
- 34:17Q&A
related talks
34mPanel: OpenTelemetry: Bridging Platform and Enablement
01h 08mOpenTelemetry: Panel Discussion and Q&A
20mObservability and Open Telemetry
30mPanel: Telemetry That Matters
37mHow To Adopt OpenTelemetry in an Enterprise Where Incumbent Vendor Tools Reign Supre...
22mBridging the OpenTelemetry Adoption Gap in Cloud-Native Applications
35mOpenTelemetry for Busy People
19mOpenTelemetry's Path to Observability's Future
