Built-in OpenTelemetry support in Elasticsearch clients
summary
Elastic added built-in OpenTelemetry to most Elasticsearch clients (Java, .NET, PHP, Ruby, Node) and creates an Elastic clients semantic conventions spec accepted into OpenTelemetry. A .NET demo sends traces to Jaeger and Elastic APM with only an OTLP exporter—no agent—and shows one span per Elasticsearch call containing cluster, node and index attributes. Implementation handles naming, cardinality and sensitive-data choices, lands in client repos via PRs, and works end‑to‑end in Elastic’s tooling.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 1:45Live demo setup
- 5:40OpenTelemetry basics
- 11:16Why built-in instrumentation
- 16:35Semantic conventions for Elasticsearch
- 19:49Demo in Elastic APM
- 23:45Challenges and future
related talks
01h 08mOpenTelemetry: The First Release, What’s Next, and How to Get Involved
46mThe State of OpenTelemetry
32mOpenTelemetry feat. logs, metrics and traces
20mObservability and Open Telemetry
28mGetting Started with OpenTelemetry
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
43mWhat is this OpenTelemetry thing?
39mMonitoring Elixir With OpenTelemetry