Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add details about the traceparent header #23075

Merged
merged 3 commits into from
May 14, 2024
Merged

Add details about the traceparent header #23075

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8a24ea1
Add details about the traceparent header
rtrieu May 8, 2024
9cb9591
trace context and datadog headers used by default
rtrieu May 13, 2024
d54e20b
remove dupe info
rtrieu May 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/real_user_monitoring/guide/browser-sdk-upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ In v5, the default `sessionReplaySampleRate` is 0 instead of 100. If you don't i

To promote the support and usage of OpenTelemetry, the default propagator types have been changed to include `tracecontext` in addition to `datadog`.

**Action to take**: If you are not already specifying the desired propagator on the `allowedTracingUrls` initialization parameter, configure your server Access-Control-Allow-Headers to also accept `traceparent` header. For more information, see [connect RUM and Traces][25].
**Action to take**: If you are not already specifying the desired propagator on the `allowedTracingUrls` initialization parameter, configure your server Access-Control-Allow-Headers to also accept the `traceparent` header. For more information, see [connect RUM and Traces][25].

### Session plan field

Expand Down
5 changes: 4 additions & 1 deletion content/en/real_user_monitoring/platform/connect_rum_and_traces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -509,7 +509,7 @@ RUM supports several propagator types to connect resources with backends that ar

## How are RUM resources linked to traces?

Datadog uses the distributed tracing protocol and sets up the following HTTP headers:
Datadog uses the distributed tracing protocol and sets up the HTTP headers below. By default, both trace context and Datadog-specific headers are used.
{{< tabs >}} {{% tab "Datadog" %}}
`x-datadog-trace-id`
: Generated from the Real User Monitoring SDK. Allows Datadog to link the trace with the RUM resource.
Expand All @@ -524,6 +524,9 @@ Datadog uses the distributed tracing protocol and sets up the following HTTP hea
: To make sure that the Agent keeps the trace.
{{% /tab %}}
{{% tab "W3C Trace Context" %}}

The W3C Trace Context header is sent by default. This means you need to configure `traceparent` for CORS servers in addition to the default Datadog-specific headers.
rtrieu marked this conversation as resolved.
Show resolved Hide resolved
bcaudan marked this conversation as resolved.
Show resolved Hide resolved

`traceparent: [version]-[trace id]-[parent id]-[trace flags]`
: `version`: The current specification assumes version is set to `00`.
: `trace id`: 128 bits trace ID, hexadecimal on 32 characters. The source trace ID is 64 bits to keep compatibility with APM.
Expand Down