Add documentation for enabling OTLP traces in APM SDKs#36498
Open
zacharycmontoya wants to merge 1 commit intomasterfrom
Open
Add documentation for enabling OTLP traces in APM SDKs#36498zacharycmontoya wants to merge 1 commit intomasterfrom
zacharycmontoya wants to merge 1 commit intomasterfrom
Conversation
mcculls
reviewed
May 5, 2026
Contributor
mcculls
left a comment
mcculls
left a comment
There was a problem hiding this comment.
LGTM from an SDK perspective
Contributor
Preview links (active after the
|
buraizu
reviewed
May 6, 2026
Contributor
buraizu
left a comment
buraizu
left a comment
There was a problem hiding this comment.
Thanks for the PR, just requesting some minor updates and posted a question
| : **Description**: Enables the Datadog SDK's OpenTelemetry interoperability for traces. <br> | ||
| **Default**: `false`<br> | ||
| **Notes**: The default is `true` in the Java SDK. | ||
| **Notes**: This configuration only enables the OpenTelemetry Tracing API. See `OTEL_TRACES_EXPORTER` to emit traces using OTLP. |
Contributor
There was a problem hiding this comment.
Suggested change
| **Notes**: This configuration only enables the OpenTelemetry Tracing API. See `OTEL_TRACES_EXPORTER` to emit traces using OTLP. | |
| **Note**: This configuration only enables the OpenTelemetry Tracing API. See `OTEL_TRACES_EXPORTER` to emit traces using OTLP. |
| : **Description**: Specifies the timeout (in milliseconds) for a single outgoing OTLP logs request. Takes precedence over the general `OTEL_EXPORTER_OTLP_TIMEOUT`. <br> | ||
| **Default**: `10000` (10s). | ||
|
|
||
| ### Traces-specific OTLP configuration |
Contributor
There was a problem hiding this comment.
Suggested change
| ### Traces-specific OTLP configuration | |
| ### Trace-specific OTLP configuration |
| `OTEL_TRACES_EXPORTER` | ||
| : **Description**: Specifies the trace exporter to be used. <br> | ||
| **Accepted values**: `otlp`, `none`. A value of `none` disables the emission of OTel and Datadog traces. <br> | ||
| **Default**: `otlp` |
Contributor
There was a problem hiding this comment.
Suggested change
| **Default**: `otlp` | |
| **Default**: `otlp`<br> |
| | Signal Source | Protocol | Port | Destination Component | | ||
| |---------------|----------|------|----------------------| | ||
| | OTel Metrics and Logs API | OTLP (gRPC/HTTP) | 4317 / 4318 | Datadog Agent OTLP Receiver or DDOT Collector | | ||
| | OTel Metrics, Logs, and Traces | OTLP (gRPC/HTTP) | 4317 / 4318 | Datadog Agent OTLP Receiver or DDOT Collector | |
Contributor
There was a problem hiding this comment.
This uses the order Metrics, Logs, and Traces but the other file (line 51) uses Traces, Metrics, and Logs. Should one or the other be updated for consistency?
Comment on lines
+274
to
+275
| **Notes**: The Java SDK requires `DD_TRACE_OTEL_ENABLED=true` for this configuration to take effect.<br> | ||
| OTLP export is not available for the Ruby, PHP, or Rust language SDKs. |
Contributor
There was a problem hiding this comment.
Suggested change
| **Notes**: The Java SDK requires `DD_TRACE_OTEL_ENABLED=true` for this configuration to take effect.<br> | |
| OTLP export is not available for the Ruby, PHP, or Rust language SDKs. | |
| **Notes**: | |
| - The Java SDK requires `DD_TRACE_OTEL_ENABLED=true` for this configuration to take effect. | |
| - OTLP export is not available for the Ruby, PHP, or Rust SDKs. |
Contributor
There was a problem hiding this comment.
Two suggestions here:
- Remove
languageas this seems to be the only place in the file that SDKs are referred to aslanguage SDKs. - Add the two distinct notes as an unordered list to make them easier to notice and scan.
duncanhewett
reviewed
May 6, 2026
Contributor
duncanhewett
left a comment
duncanhewett
left a comment
There was a problem hiding this comment.
Somewhere (can be a separate PR) we'll need to document use cases for OTLP export, current limitations (semantics etc), what features work with different setups, etc.
I also think we should label OTLP export as preview for now.
| `OTEL_TRACES_EXPORTER` | ||
| : **Description**: Specifies the trace exporter to be used. <br> | ||
| **Accepted values**: `otlp`, `none`. A value of `none` disables the emission of OTel and Datadog traces. <br> | ||
| **Default**: `otlp` |
Contributor
There was a problem hiding this comment.
I didn't think the default was otlp. Isn't the default null meaning don't export traces in OTLP?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Documents how to configure the APM SDKs to export traces using OTLP rather than the default Datadog protocol. This allows users to send traces to any OTLP-compatible receiver, rather than just the Datadog Agent.
This change was recently released in several language SDKs.
Merge instructions
N/A
Merge readiness:
AI assistance
N/A
Additional notes
N/A