Use W3C tracecontext instead of x-request-id
#30.052 aberto em 10 de out. de 2023
Métricas do repositório
- Stars
- (27.997 stars)
- Métricas de merge de PR
- (Mesclagem média 8d) (378 fundiu PRs em 30d)
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:]
- https://istio.io/latest/docs/tasks/observability/distributed-tracing/overview/
- https://github.com/envoyproxy/envoy/blob/a9ae08bea8964a4deda789c12578777e7f3657ce/docs/root/intro/arch_overview/observability/tracing.rst#L13
- https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#x-client-trace-id