From df15bee882bb893b168ed7732c100620feca0d20 Mon Sep 17 00:00:00 2001 From: Tushar Date: Wed, 23 Oct 2024 10:17:22 -0400 Subject: [PATCH] Address more --- content/en/tracing/glossary/_index.md | 5 +++-- .../trace_collection/trace_context_propagation/_index.md | 1 - 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/tracing/glossary/_index.md b/content/en/tracing/glossary/_index.md index 10aa3dc344a13..c8449148728de 100644 --- a/content/en/tracing/glossary/_index.md +++ b/content/en/tracing/glossary/_index.md @@ -111,7 +111,7 @@ To learn more, read [Application Instrumentation][26]. Baggage allows you to propagate key-value pairs (also known as baggage items) across service boundaries in a distributed system. Unlike trace context, which focuses on trace identifiers, baggage allows for the transmission of business data and other contextual information alongside traces. -To learn more, read supported [propagation formats][27] for your application's language. +To learn more, read supported [propagation formats][28] for your application's language. ## Further Reading @@ -142,4 +142,5 @@ To learn more, read supported [propagation formats][27] for your application's l [24]: /tracing/trace_collection/automatic_instrumentation/single-step-apm [25]: /tracing/trace_collection/automatic_instrumentation/dd_libraries/ [26]: /tracing/trace_collection/ -[27]: /tracing/trace_collection/trace_context_propagation/#supported-formats \ No newline at end of file +[27]: /tracing/trace_collection/trace_context_propagation +[28]: /tracing/trace_collection/trace_context_propagation/#supported-formats \ No newline at end of file diff --git a/content/en/tracing/trace_collection/trace_context_propagation/_index.md b/content/en/tracing/trace_collection/trace_context_propagation/_index.md index 7e3e29c720a67..37258defb98e5 100644 --- a/content/en/tracing/trace_collection/trace_context_propagation/_index.md +++ b/content/en/tracing/trace_collection/trace_context_propagation/_index.md @@ -47,7 +47,6 @@ Use the following environment variables to configure formats for reading and wri **Default**: `datadog,tracecontext`
**Note**: With multiple formats, extraction follows the specified order (for example, `datadog,tracecontext` checks Datadog headers first). The first valid context continues the trace; additional valid contexts become span links. - `OTEL_PROPAGATORS` : Specifies trace context propagation formats for both extraction and injection (comma-separated list). Lowest precedence; ignored if any other Datadog trace context propagation environment variable is set.
**Note**: Only use this configuration when migrating an application from the OpenTelemetry SDK to the Datadog SDK. For more information on this configuration and other OpenTelemetry environment variables, see [Using OpenTelemetry Environment Variables with Datadog SDKs][9].