envoyproxy/envoy

Use W3C tracecontext instead of x-request-id

Open

#30.052 aperta il 10 ott 2023

Vedi su GitHub
 (6 commenti) (22 reazioni) (0 assegnatari)C++ (5373 fork)batch import
area/opentelemetryarea/tracingenhancementhelp wanted

Metriche repository

Star
 (27.997 star)
Metriche merge PR
 (Merge medio 8g) (378 PR mergiate in 30 g)

Descrizione

Title: Use W3C tracecontext instead of x-request-id

Description: W3C tracecontext (https://www.w3.org/TR/trace-context/) could be used instead of x-request-id (https://http.dev/x-request-id) header to carry request ID and sampling decision.

The propagation of the header x-request-id is not supported by other ecosystems that implement automatic in-process header propagation e.g. OpenTelmetry auto-instrumentation libraries.

The OpenTelemetry auto-instrumentation simplifies header propagation for tracing capabilities in Envoy. The OTEL SDK has official support for B3 multi (used by envoy), Jaeger and W3C tracecontext.

It seems unlikely that OpenTelemetry will support x-request-id header propagators across languages https://github.com/open-telemetry/opentelemetry-specification/issues/2912

[optional Relevant Links:]

Guida contributor