From 71ca133a797891ebb087ef010b6de6c609902e00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Tue, 14 Nov 2023 15:18:33 +0100 Subject: [PATCH 1/3] Refer to W3C Baggage working draft --- specification/protocol/exporter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/protocol/exporter.md b/specification/protocol/exporter.md index 2b0ef9109ec..ade8ac90e6b 100644 --- a/specification/protocol/exporter.md +++ b/specification/protocol/exporter.md @@ -155,7 +155,7 @@ release). ### Specifying headers via environment variables -The `OTEL_EXPORTER_OTLP_HEADERS`, `OTEL_EXPORTER_OTLP_TRACES_HEADERS`, `OTEL_EXPORTER_OTLP_METRICS_HEADERS` environment variables will contain a list of key value pairs, and these are expected to be represented in a format matching to the [W3C Correlation-Context](https://github.com/w3c/baggage/blob/master/baggage/HTTP_HEADER_FORMAT.md), except that additional semi-colon delimited metadata is not supported, i.e.: key1=value1,key2=value2. All attribute values MUST be considered strings. +The `OTEL_EXPORTER_OTLP_HEADERS`, `OTEL_EXPORTER_OTLP_TRACES_HEADERS`, `OTEL_EXPORTER_OTLP_METRICS_HEADERS` environment variables will contain a list of key value pairs, and these are expected to be represented in a format matching to the [W3C Baggage](https://www.w3.org/TR/baggage/#header-content), except that additional semi-colon delimited metadata is not supported, i.e.: key1=value1,key2=value2. All attribute values MUST be considered strings. ## Retry From 024a4fb7a6e131fcd58ffbc414e4d002e7ebafbe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Tue, 14 Nov 2023 15:20:11 +0100 Subject: [PATCH 2/3] Update sdk.md --- specification/resource/sdk.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/resource/sdk.md b/specification/resource/sdk.md index 86e83ee215f..2c3df621323 100644 --- a/specification/resource/sdk.md +++ b/specification/resource/sdk.md @@ -137,7 +137,7 @@ has higher priority. The `OTEL_RESOURCE_ATTRIBUTES` environment variable will contain of a list of key value pairs, and these are expected to be represented in a format matching -to the [W3C Baggage](https://w3c.github.io/baggage), except that additional +to the [W3C Baggage](https://www.w3.org/TR/baggage/#header-content), except that additional semi-colon delimited metadata is not supported, i.e.: `key1=value1,key2=value2`. All attribute values MUST be considered strings and characters outside the `baggage-octet` range MUST be percent-encoded. From cd9eee497049027a8838aead7ad6962b6b8728b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Tue, 14 Nov 2023 15:29:53 +0100 Subject: [PATCH 3/3] Update other references --- specification/baggage/api.md | 2 +- specification/context/api-propagators.md | 4 ++-- specification/logs/README.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/specification/baggage/api.md b/specification/baggage/api.md index ffccfe17fe8..fb6cb392ede 100644 --- a/specification/baggage/api.md +++ b/specification/baggage/api.md @@ -146,7 +146,7 @@ reasons. The API layer or an extension package MUST include the following `Propagator`s: -* A `TextMapPropagator` implementing the [W3C Baggage Specification](https://w3c.github.io/baggage). +* A `TextMapPropagator` implementing the [W3C Baggage Specification](https://www.w3.org/TR/baggage). See [Propagators Distribution](../context/api-propagators.md#propagators-distribution) for how propagators are to be distributed. diff --git a/specification/context/api-propagators.md b/specification/context/api-propagators.md index a1c85ee0f6c..762b309ef01 100644 --- a/specification/context/api-propagators.md +++ b/specification/context/api-propagators.md @@ -333,9 +333,9 @@ Required parameters: The official list of propagators that MUST be maintained by the OpenTelemetry organization and MUST be distributed as OpenTelemetry extension packages: -* [W3C TraceContext](https://www.w3.org/TR/trace-context/). MAY alternatively +* [W3C TraceContext](https://www.w3.org/TR/trace-context). MAY alternatively be distributed as part of the OpenTelemetry API. -* [W3C Baggage](https://w3c.github.io/baggage). MAY alternatively +* [W3C Baggage](https://www.w3.org/TR/baggage). MAY alternatively be distributed as part of the OpenTelemetry API. * [B3](https://github.com/openzipkin/b3-propagation). * [Jaeger](https://www.jaegertracing.io/docs/latest/client-libraries/#propagation-format). diff --git a/specification/logs/README.md b/specification/logs/README.md index b0c3fb5acbe..eaf1ab28212 100644 --- a/specification/logs/README.md +++ b/specification/logs/README.md @@ -284,7 +284,7 @@ auto-instrumenting solutions that modify trace logging libraries used by the application to automatically output the trace context such as the trace id or span id with every log statement. The trace context can be automatically extracted from incoming requests if standard compliant request propagation is -used, e.g. via [W3C TraceContext](https://w3c.github.io/trace-context/). In +used, e.g. via [W3C TraceContext](https://www.w3.org/TR/trace-context). In addition, the requests outgoing from the application may be injected with the same trace context data, thus resulting in context propagation through the application and creating an opportunity to have full trace context in logs