zipkin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Cole <>
Subject Re: headers in response
Date Sat, 15 Dec 2018 06:03:10 GMT
This topic has come up many times. Somebody named Jordi raise this
over 2 years ago I think :)

The best solution I can think of is to have the user opt into a
response header. This is what kamon does and I think some libraries
could follow:

main downside besides leaking the ID is that most instrumentation are
not currently trying to mutate http response headers. At any rate, in
a lot of middleware someone can do this any way by adding a filter
that peeks at the current span.

hope this helps!
On Sat, Dec 15, 2018 at 1:44 PM Jordi Polo Carres <> wrote:
> Hi,
> Multiple times I've been asked in my company about adding the zipkin
> headers to responses.
> Mostly by testers who want to know and search trace ids in logs but they
> are doing some manual test and it is difficult for them to generate unique
> ids and add them to the headers.
> As this is not a case that happens in real production environment, I never
> wanted to do it.
> What do other libraries do? Is this something you can relate to?
> Thanks
> --
> *Jordi Polo Carres* | API bundle lead | Medidata Solutions Worldwide
> <>
> Api bundle:
> API standard:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message