Elastic announced the availability of its managed OpenTelemetry Protocol (OTLP) endpoint in Elastic Observability, reducing the need for deploying and fine-tuning multiple collectors, and allowing SREs to send data directly from any OpenTelemetry (OTel) compatible source into Elastic Cloud.
SREs managing OpenTelemetry ingestion often deploy multiple layers of OTel Collectors, juggling scaling and resource demands at each tier. As applications grow and telemetry volumes rise, they must continually configure and maintain this infrastructure, which is a time-consuming and difficult process to scale.
Elastic’s managed OTLP endpoint reduces the need for deploying and fine-tuning multiple collectors for OTLP data ingestion from various sources. The OTLP endpoint is fully managed by Elastic and auto-scales across production environments, minimizing the time spent on managing OTel ingest infrastructure. With the Elastic managed OTLP endpoint, OpenTelemetry data is stored without any schema translation, preserving both semantic conventions and resource attributes.
“No matter where they’re building, SREs would rather focus on finding answers over ingestion plumbing,” said Santosh Krishnan, general manager, Observability & Security at Elastic. “The managed OTLP endpoint for Elastic Observability allows SREs to focus on analyzing application telemetry with Elastic’s built-in AI capabilities, all while embracing the OpenTelemetry data model preserved with original attributes in Elastic.”