We’re excited to announce the managed OTLP endpoint for Elastic Observability serverless. This feature marks a major milestone in Elastic’s shift to OpenTelemetry as the backbone of our data ingestion strategy and makes it dramatically easier to get high-fidelity OpenTelemetry data into Elastic Cloud.
What is Elastic’s Managed OTLP Endpoint?
The managed OTLP endpoint delivers on that promise offering a fully hosted OpenTelemetry ingestion path that’s scalable, reliable, and designed from the ground up for OpenTelemetry.
Data from OpenTelemetry sDKs, OpenTelemetry Collectors, or any OTLP service can send data to the OTLP endpoint. The OTLP endpoint is available on Elastic Cloud serverless, and is fully managed by Elastic. This helps minimize the burden on customers of managing the OpenTelemetry ingestion layer. Whenever your production environment scales, the OTLP end point will also auto scale without any management from an sRE.
OpenTelemetry data is stored without any schema translation, preserving both semantic conventions and resource attributes. Additionally, it supports ingesting OTLP logs, metrics, and traces in a unified manner, ensuring consistent treatment across all telemetry data. This marks a significant improvement over the existing functionality, which primarily focuses on traces and APM use cases.
Hence, sREs gain:
-
Native OTLP ingestion with Elastic-managed reliability and scale
-
OTel-native data storage, enabling richer analytics and future-proof observability
-
Elastic-grade scaling, ready for production and multi-tenant workloads
-
Frictionless onboarding, with a drop-in endpoint for logs, metrics and traces..
Native OTLP ingestion
Whether you are using native OTel sDKs, OpenTelemetry Collector, EDOT, or other OpenTelemetry instrumentation, the OTLP endpoint will ingest any native OTLP data.
The managed OTLP endpoint will automatically scale with Observability data that is notoriously bursty. A sudden spike in requests, a scaling event in Kubernetes, or a deployment gone sideways can lead to massive surges in telemetry, often when you need visibility the most. That’s exactly what the managed OTLP endpoint in Elastic Observability serverless is built to handle.
This isn’t just a thin wrapper on a collector. It’s a multi-tenant, auto-scaling service architected to absorb high volumes of OpenTelemetry data without you having to manage infrastructure, pre-provision capacity, or worry about dropped data.
Whether you’re routing data directly from OpenTelemetry sDKs or via an intermediate Collector, Elastic handles the scale behind the scenes. The endpoint is designed to scale with your telemetry traffic and recover gracefully from bursts, giving you one less thing to monitor. Just point your instrumentation at the endpoint and let Elastic take care of the rest.
Natively stored OpenTelemetry
With this feature, developers can now send OpenTelemetry signals directly to an Elastic Cloud serverless project using the OTLP output of a collector or sDK regardless of the distribution contrib, EDOT and any other distribution will work).
The endpoint also supports data forwarded from any OpenTelemetry Collectors, sDKs or OTLP compliant forwarder. This gives teams full control to send directly from an sDK or route, enrich, or batch telemetry when needed. Elasticsearch stores OpenTelemetry data using the OpenTelemetry data model, including resource attributes, to identify emitting entities and enable Es|QL queries that correlate logs, metrics, and traces.
Faster time-to-insight
Whether you’re building in serverless, Kubernetes, or classic VMs, this endpoint lets you focus on instrumentation and insights—not ingestion plumbing. It dramatically shortens the time from telemetry to value, while embracing the OpenTelemetry data model by preserving the original attributes and built-in correlation
Easy connectivity to Managed OTLP Endpoint
Connecting to the Managed OTLP endpoint is as simple as setting your sDK or the OTel collector OTLP export setting to the Elastic Managed OTLP Endpoint URL, and authentication key. Getting your endpoint is extremely straight-forward, go to project management, then edit alias and you will find your project’s OTLP endpoint.
Get started Today
The managed OTLP endpoint can be used today on Elastic Observability serverless. support for Elastic Cloud Hosted deployments is coming soon.
For more detail and examples, follow this guide.
Whether you’re running microservices in Kubernetes, workloads in serverless, or apps on classic VMs, the OTLP endpoint helps you streamline your observability pipeline, standardize on OpenTelemetry, and accelerate your mean time to resolution (MTTR).
Also check out our OTel resources about instrumenting and ingesting OTel into Elastic
Elastic Distributions of OpenTelemetry
Monitoring Kubernetes with Elastic and OpenTelemetry
Dynamic workload discovery with EDOT Collector
Assembling an OpenTelemetry NGINX Ingress Controller Integration