OTLP Intake for Managed Platforms
Overview
Datadog provides dedicated OTLP intake endpoints for managed platforms, allowing you to send traces, metrics, and logs directly to Datadog with minimal configuration. Each supported platform has its own OTLP subdomain (for example, cloudflare.integrations.otlp.datadoghq.com). These dedicated endpoints allow Datadog to identify the traffic source and apply platform-specific processing and attribution. The generic OTLP endpoint assumes a host is present, which can cause unexpected behavior for managed platform traffic.
Use this option when you run workloads on a managed platform where installing a Datadog Agent or OpenTelemetry Collector is not feasible. If your platform is not in the table below and you run on AWS, Azure, or GCP serverless compute, see Serverless.
Each endpoint supports the following signal paths:
| Signal | Path |
|---|
| Traces | /v1/traces |
| Metrics | /v1/metrics |
| Logs | /v1/logs |
For signal-specific configuration (metric translation, log processing), see the Logs and Metrics endpoint pages.
Configuration
To send OTLP data to Datadog through a managed platform endpoint, configure your OpenTelemetry exporter with the following environment variables. Replace {platform} with your platform’s subdomain from the supported platforms table.
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
export OTEL_EXPORTER_OTLP_ENDPOINT="https://{platform}.integrations.otlp."
export OTEL_EXPORTER_OTLP_HEADERS="dd-api-key=${DD_API_KEY}"
To send only traces:
export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL="http/protobuf"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://{platform}.integrations.otlp./v1/traces"
export OTEL_EXPORTER_OTLP_TRACES_HEADERS="dd-api-key=${DD_API_KEY}"
Managed platform endpoints do not use the dd-otlp-source header. If you migrate from the generic OTLP endpoint, remove this header from your configuration.
All endpoints follow the pattern https://{subdomain}.integrations.otlp./.
To enable OTLP export from a managed platform not listed above, contact your Customer Success Manager.
Limitations
Without a Collector or Agent, telemetry is not enriched with host metadata. Features that depend on this metadata (for example, the Infrastructure Host List) are unavailable. See the OpenTelemetry compatibility list for the full list of affected features.
Limited normalization
Some signal processing that a Collector or Agent performs automatically does not happen with direct ingest. For example, cumulative-to-delta metric conversion requires a stateful component. If your platform exports cumulative metrics, configure your SDK or pipeline to export delta temporality.
Trace metrics
Trace metrics are computed by default for managed platform endpoints. Managed platforms may sample traffic before export, which can affect trace metric accuracy.
Sampling
Sampling controls available in the Collector (tail-based sampling, probabilistic sampling) are not available with direct ingest. Managed platforms may apply their own sampling before export.
Further reading
Additional helpful documentation, links, and articles:
