---
title: Export Traces from Datadog SDKs in OTLP Format
description: >-
  Configure a Datadog SDK to export traces in OpenTelemetry Protocol (OTLP)
  format to a DDOT Collector or any OTLP-compatible receiver.
breadcrumbs: >-
  Docs > OpenTelemetry in Datadog > Instrument Your Applications > Using Datadog
  SDKs with OpenTelemetry > Export Traces from Datadog SDKs in OTLP Format
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Export Traces from Datadog SDKs in OTLP Format

{% callout %}
##### Preview

OTLP trace export from Datadog SDKs is in Preview. To provide feedback or request support, contact your Datadog account team.
{% /callout %}

Datadog SDKs can export traces in [OTLP](https://opentelemetry.io/docs/specs/otlp/) format to an OTLP-compatible receiver, including [DDOT](https://docs.datadoghq.com/opentelemetry/setup/ddot_collector.md) or any OpenTelemetry Collector.

## Prerequisites{% #prerequisites %}

OTLP export requires:

- **The Datadog SDK installed and attached to your service.** OTLP export uses your existing Datadog SDK setup. You don't need to configure the Datadog Agent for native trace export, because OTLP export sends traces to a receiver instead.
- **An OTLP-compatible receiver that forwards data to Datadog**, such as the [DDOT Collector](https://docs.datadoghq.com/opentelemetry/setup/ddot_collector.md) or an [OpenTelemetry Collector](https://docs.datadoghq.com/opentelemetry/setup/collector_exporter.md). OTLP export sends data to a receiver rather than directly to Datadog, so the receiver must be reachable from your instrumented service. For production workloads, Datadog recommends DDOT for batching, performance, and processing benefits. You aren't required to use DDOT.

## Language support{% #language-support %}

Select your language to see the minimum SDK version and supported OTLP protocols.

{% tab title="Java" %}

- **Minimum version**: v1.62.0
- **Supported protocols**: `http/protobuf` (default), `grpc`

{% /tab %}

{% tab title="Python" %}

- **Minimum version**: v4.8.0
- **Supported protocols**: `http/json`

{% /tab %}

{% tab title="Node.js" %}

- **Minimum version**: v5.98.0
- **Supported protocols**: `http/json`

{% /tab %}

{% tab title="Go" %}

- **Minimum version**: v2.8.0
- **Supported protocols**: `http/protobuf`

{% /tab %}

{% tab title=".NET" %}

- **Minimum version**: v3.41.0
- **Supported protocols**: `http/json` (default), `http/protobuf` (v3.45.0+)

{% /tab %}

**Note**: The OpenTelemetry specification defaults OTLP to `http/protobuf`, but Datadog SDK defaults vary by language. Python, Node.js, and .NET default to `http/json`, while Java and Go default to `http/protobuf`. Where a language supports multiple protocols, set `OTEL_EXPORTER_OTLP_PROTOCOL` or `OTEL_EXPORTER_OTLP_TRACES_PROTOCOL` to override the default. Make sure your receiver accepts the protocol you use. By convention, OTLP/HTTP (`http/protobuf` or `http/json`) uses port `4318`, and OTLP/gRPC (`grpc`) uses port `4317`.

## Enable OTLP trace export{% #enable-otlp-trace-export %}

To export traces in OTLP format, set the following environment variables on the instrumented service:

```shell
OTEL_TRACES_EXPORTER=otlp
DD_TRACE_OTEL_ENABLED=true
```

By default, traces are sent to `http://localhost:4318/v1/traces`.

To send traces to a different endpoint, set `OTEL_EXPORTER_OTLP_ENDPOINT` or the trace-specific `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`. See the [OTLP Exporter Configuration](https://opentelemetry.io/docs/specs/otel/protocol/exporter/) documentation for details.

## Verify{% #verify %}

After you enable OTLP export and your service receives traffic, confirm that traces appear in the [Trace Explorer](https://docs.datadoghq.com/tracing/trace_explorer.md). If traces don't arrive, verify that your [receiver](https://docs.datadoghq.com/opentelemetry/setup.md) is running, reachable at the configured endpoint, and forwarding data to Datadog.

## Current limitations{% #current-limitations %}

- OTLP trace export is in Preview and supports core APM functionality for automatic and manually created traces. Other Datadog features and capabilities may not be supported, or may require the Datadog Agent even if traces are not sent through it.
- Traces are exported with Datadog semantics. For example, an HTTP status code is represented as `http.status_code` in Datadog semantics and `http.response.status_code` in OTel semantics.

For details on which Datadog features each setup supports, see the [feature compatibility table](https://docs.datadoghq.com/opentelemetry/compatibility.md#feature-compatibility).

## Further reading{% #further-reading %}

- [Using Datadog SDKs with OpenTelemetry](https://docs.datadoghq.com/opentelemetry/instrument/dd_sdks.md)
- [Datadog Distribution of the OpenTelemetry Collector (DDOT)](https://docs.datadoghq.com/opentelemetry/setup/ddot_collector.md)
- [Datadog APM](https://docs.datadoghq.com/tracing.md)