envoyproxy/envoy

Use W3C tracecontext instead of x-request-id

Open

#30 052 ouverte le 10 oct. 2023

Voir sur GitHub
 (6 commentaires) (22 réactions) (0 assignés)C++ (5 373 forks)batch import
area/opentelemetryarea/tracingenhancementhelp wanted

Métriques du dépôt

Stars
 (27 997 stars)
Métriques de merge PR
 (Merge moyen 8j) (378 PRs mergées en 30 j)

Description

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:]

Guide contributeur