Re: Envoy tracing with opentelemetry - Headers propagation

[Yan Avlasov]

I suggest filing an Issue on GitHub where it can be discussed further.

On Tue, Jan 14, 2025 at 4:12 PM 'Lautaro Bazalo' via envoy-users <envoy...@googlegroups.com> wrote:

Hi everyone,

I'm part of the platform engineering team, and we are developing tracing in our delivery and observability platform.
I was reading the documentation about tracing and started some PoCs. In summary, the PoC consists of Envoy, two services, an OpenTelemetry Collector, and Grafana with Tempo. The test involved making a request from a client to Service A, which then made another request to Service B. Finally, Service B responded to Service A, which then responded to the client.

The result showed that we only need to propagate the "traceparent" header between the services, which led to our current question. The Envoy tracing documentation states:

"Whichever tracing provider is being used, the service should propagate the x-request-id to enable logging across the invoked services to be correlated."

This seems to contradict our findings. What should we do in this case?

--
You received this message because you are subscribed to the Google Groups "envoy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to envoy-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/envoy-users/939a701b-db49-4b7b-a08e-655e2cd0e7b7n%40googlegroups.com.