--- title: OTLP Intake for Managed Platforms description: >- Send traces, metrics, and logs from managed platforms like Cloudflare, Vercel, and Heroku directly to Datadog through dedicated OTLP endpoints. breadcrumbs: >- Docs > OpenTelemetry in Datadog > Send OpenTelemetry Data to Datadog > Datadog OTLP Intake Endpoint > OTLP Intake for Managed Platforms --- > For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt). # OTLP Intake for Managed Platforms ## Overview{% #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](https://docs.datadoghq.com/opentelemetry/otlp_ingest_in_the_agent.md) or [OpenTelemetry Collector](https://docs.datadoghq.com/opentelemetry/setup/collector_exporter.md) is not feasible. If your platform is not in the table below and you run on AWS, Azure, or GCP serverless compute, see [Serverless](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/serverless.md). {% alert level="danger" %} Host metadata sent to managed platform endpoints does not populate the [Infrastructure Host List](https://docs.datadoghq.com/infrastructure/list.md). {% /alert %} 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](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/logs.md) and [Metrics](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/metrics.md) endpoint pages. ## Configuration{% #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. ```shell 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: ```shell 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}" ``` {% alert level="info" %} 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. {% /alert %} ## Supported platforms{% #supported-platforms %} All endpoints follow the pattern `https://{subdomain}.integrations.otlp. /`. | Platform | Subdomain | Setup guide | | -------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------- | | AWX | `awx` | — | | Buildkite | `buildkite` | [Buildkite OpenTelemetry](https://buildkite.com/docs/pipelines/integrations/observability/opentelemetry) | | Claude | `claude` | — | | Cloudflare | `cloudflare` | [Cloudflare Workers observability](https://developers.cloudflare.com/workers/observability/exporting-opentelemetry-data/) | | Cribl | `cribl` | — | | GitHub Actions | `github-actions` | — | | Grafbase | `grafbase` | [Grafbase observability](https://grafbase.com/docs/gateway/observability) | | Heroku | `heroku` | [Heroku telemetry](https://devcenter.heroku.com/articles/heroku-telemetry) | | IBM | `ibm` | — | | LangSmith | `langsmith` | — | | LiveCloudKit | `livekit` | — | | Modal | `modal` | [Modal OpenTelemetry](https://modal.com/docs/guide/otel-integration) | | MuleSoft | `mulesoft` | [MuleSoft Telemetry Exporter](https://docs.mulesoft.com/monitoring/telemetry-exporter) | | Netlify | `netlify` | — | | OpenTofu | `opentofu` | — | | Retool | `retool` | [Retool performance monitoring](https://docs.retool.com/apps/guides/observability/performance-monitoring) | | RWX | `rwx` | — | | Salesforce | `sfdc` | — | | Shopify | `shopify` | — | | Solace | `solace` | — | | Spacelift | `spacelift` | — | | Supabase | `supabase` | — | | Svix | `svix` | — | | Trigger.dev | `triggerdev` | — | | Vercel | `vercel` | [Vercel Marketplace](https://vercel.com/marketplace/datadog) | To enable OTLP export from a managed platform not listed above, contact your Customer Success Manager. ## Limitations{% #limitations %} ### No metadata enrichment{% #no-metadata-enrichment %} Without a Collector or Agent, telemetry is not enriched with host metadata. Features that depend on this metadata (for example, the [Infrastructure Host List](https://docs.datadoghq.com/infrastructure/list.md)) are unavailable. See the [OpenTelemetry compatibility list](https://docs.datadoghq.com/opentelemetry/compatibility.md) for the full list of affected features. ### Limited normalization{% #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 %} [Trace metrics](https://docs.datadoghq.com/tracing/metrics.md) are computed by default for managed platform endpoints. Managed platforms may sample traffic before export, which can affect trace metric accuracy. ### Sampling{% #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{% #further-reading %} - [OpenTelemetry Compatibility in Datadog](https://docs.datadoghq.com/opentelemetry/compatibility.md) - [Datadog OTLP Intake Endpoint](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest.md)