OpenTelemetry (OTel) provides a standardized way of collecting and exporting telemetry data. It allows applications and infrastructure to transmit telemetry to backends (such as Dynatrace) using vendor-agnostic formats. These backends can then aggregate and analyze the data.
You can implement this service by service, adopting the open standards of OpenTelemetry where openness matters most, while leveraging enhanced OneAgent features available where you need them. Dynatrace supports this flexible approach, ensuring you experience industry-leading analytics regardless of how you mix your instrumentation choices.
There are two different ways you can export your OTLP data to Dynatrace. Choose the deployment option that best aligns with your observability strategy.

Send OTLP traces, metrics, and logs to Dynatrace directly from your applications over OTLP/HTTP, or route them through an OpenTelemetry Collector that exports to the Dynatrace OTLP API. For more information about OpenTelemetry Collectors, see OTel Collector.
Dynatrace provides end-to-end observability for all your application telemetry while embracing OpenTelemetry standards. With its unified observability approach, Dynatrace offers a comprehensive platform for viewing, storing, and correlating all OpenTelemetry signals in one place. This solution empowers you to simplify complexity and innovate faster by extracting maximum value from your data, regardless of origin.
Dynatrace provides you with:
Dynatrace is deeply committed to the OpenTelemetry ecosystem through multiple avenues of involvement:
Dynatrace meets customers where they are in their observability journey, offering multiple ingestion options for getting OpenTelemetry signals into the platform including:
OpenTelemetry currently has no stable specification for Real User Monitoring (RUM). While the current specification includes semantic conventions for sessions and limited coverage of interactions, automatic user action capturing, user journey analysis, Session Replay and Core Web Vitals scoring are not specified.
Dynatrace recommendation: Use your OTel-instrumented backend together with RUM JavaScript for web applications and OneAgent for Mobile. They use the W3C trace context to link frontend requests directly to backend OTel traces, giving you end-to-end visibility from the browser and mobile app to your services. See Frontend-backend linking for how this connection works.
If adopting OTel is a firm requirement for frontend, OTel SDKs can send traces, metrics, and logs to Dynatrace via OTLP. However, you will not get RUM-specific capabilities such as frontend management, user sessions, user actions, Core Web Vitals, or Session Replay.
Licensing for OpenTelemetry data is fully integrated into the Dynatrace Platform Subscription model, ensuring that all telemetry types (traces and spans, metrics, logs) are billed transparently and consistently.
The Dynatrace Semantic Dictionary provides standardized naming conventions for metrics, logs, and spans. Using these conventions ensures optimal integration with Dynatrace analytics capabilities.
Learn more about the Semantic Dictionary at Semantic Dictionary.