We’re excited to announce general availability of Elastic Distributions of OpenTelemetry (EDOT)! EDOT is a fully open distribution of the OpenTelemetry collector and language SDKs, providing SREs and developers with a stable, production-tested OTel ecosystem backed by enterprise-grade support.
While OTel components are feature-rich, enhancements through the community can take time. Additionally, support is left up to the community or individual users and organizations. EDOT delivers the following benefits to end users:
-
Production-ready, backed by expert OTel support
-
No vendor lock-In - no proprietary add-ons
-
Preserving OpenTelemetry standards - no schema conversion
EDOT Collector and SDKs are GA
Elastic Distributions of OpenTelemetry (EDOT) is a curated collection of OpenTelemetry components, EDOT Collector and language SDKs. It is designed to support OTel telemetry from applications and shared infrastructure such as hosts or Kubernetes.
Highlighted below are all the EDOT components that are now GA.
-
Elastic Distribution of OpenTelemetry (EDOT) Collector - The EDOT Collector is the OTel collector with Elastic’s set of processors, receivers and exporters to send OTel to Elastic
-
Elastic Distribution of OpenTelemetry (EDOT) SDKs & zero-code instrumentation - Users have an option to instrument with the SDKs or choose to use zero-code instrumentation. Here are all the SDKs currently available in EDOT:
-
Elastic Distribution of OpenTelemetry (EDOT) Java.
-
Elastic Distribution of OpenTelemetry (EDOT) Python
-
Elastic Distribution of OpenTelemetry (EDOT) NodeJS
-
Elastic Distribution of OpenTelemetry (EDOT) .NET
-
Elastic Distribution of OpenTelemetry (EDOT) PHP
-
Elastic Distribution of OpenTelemetry (EDOT) iOS
-
Elastic Distribution of OpenTelemetry (EDOT) Android
-
Details and documentation for EDOT are available in our public EDOT documentation, and our EDOT github repository.
To learn more about the ease of use, particularly with Kubernetes check out our previous blog Ingest Kubernetes and application telemetry in 3 steps with EDOT.
What an SRE gains with EDOT
Production-ready, Backed by Expert OTel Support
Enterprises adopting OpenTelemetry often struggle with unreliable support, slow bug fixes, and untested updates, leading to operational risks and downtime, and increased troubleshooting efforts. Without enterprise-grade guarantees, teams are left to resolve issues on their own, increasing maintenance overhead and slowing adoption.
EDOT delivers enterprise-grade support backed by OpenTelemetry experts, ensuring stability, proactive fixes beyond OpenTelemetry’s release cycles and production-tested reliability. With rapid issue resolution and expert guidance, EDOT enables organizations to confidently adopt and scale OpenTelemetry without operational disruptions or added maintenance burden.
No Vendor Lock-In—No Proprietary Add-Ons
Observability vendors have traditionally built proprietary agents and ingestion pipelines allowing them to control data flows and lock in users.
Elastic Distributions of OpenTelemetry (EDOT) offers a fully open, vendor-neutral approach to observability. As a curated portfolio of OpenTelemetry components, EDOT enhances infrastructure and application monitoring with Elastic Observability—without proprietary modifications.
All enhancements and fixes are contributed back to the OpenTelemetry community, ensuring EDOT remains a stable, standards-compliant distribution that stays aligned with upstream OpenTelemetry. This guarantees interoperability, seamless upgrades, and freedom from vendor lock-in.
Preserving OpenTelemetry Standards for Richer Context
When vendors modify OpenTelemetry data and schemas by introducing proprietary translations that disrupt interoperability, they create vendor lock-in and increase complexity. These modifications force operations teams to manage custom integrations, convert schemas, and sometimes result in each signal requiring its own query language and tooling, adding unnecessary overhead and limiting flexibility.
Elastic has re-architected its platform with an OTel-first approach that preserves the OpenTelemetry data model. OTel data can now be used in its original specification to power Elastic dashboards, analytics, alerts, and other functionality without the need for schema conversions – it just works.
With Elasticsearch as a single backend for all OpenTelemetry signals, users can store and query observability data in a unified, OTel-native format. Combined with ES|QL, a powerful and flexible query language, SREs get effortless correlation of logs, metrics, and traces using OpenTelemetry resource attributes. The result is a faster, more intuitive way to analyze system health and performance—all in one place.
Get Started Today
EDOT is available to all Elastic customers. Whether you’re adopting OpenTelemetry for the first time or looking for a reliable distribution with enterprise-grade support, EDOT ensures a smooth, OpenTelemetry-first experience.
Check out our EDOT documentation, and our EDOT github repository and get started today!
Additionally check out some of the blogs detailing our components