Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -672,13 +672,23 @@ Datadog uses the distributed tracing protocol and sets up the HTTP headers below
: `parent id`: 64 bits span ID, hexadecimal on 16 characters.
: `trace flags`: Sampled (`01`) or not sampled (`00`)

**Trace ID Conversion**: The 128-bit W3C trace ID is created by padding the original 64-bit source trace ID with leading zeros. This ensures compatibility with APM while conforming to the W3C Trace Context specification. The original 64-bit trace ID becomes the lower 64 bits of the 128-bit W3C trace ID.

`tracestate: dd=s:[sampling priority];o:[origin]`
: `dd`: Datadog's vendor prefix.
: `sampling priority`: Set to `1` if the trace was sampled, or `0` if it was not.
: `origin`: Always set to `rum` to make sure the generated traces from Real User Monitoring don't affect your APM Index Spans counts.

Example:
: `traceparent: 00-00000000000000008448eb211c80319c-b7ad6b7169203331s-01`
**Examples**:

Source trace ID (64-bit): `8448eb211c80319c`

W3C Trace Context (128-bit): `00000000000000008448eb211c80319c`

The relationship shows that the original 64-bit trace ID `8448eb211c80319c` is padded with 16 leading zeros (`0000000000000000`) to create the 128-bit W3C trace ID.

Complete traceparent example:
: `traceparent: 00-00000000000000008448eb211c80319c-b7ad6b7169203331-01`
: `tracestate: dd=s:1;o:rum`

{{% /tab %}}
Expand Down
Loading