Adrian Cole

one way is to implement something like we have in brave, which is a generic http data policy thing. this would allow you to change the span name etc. https://github.com/openzipkin/brave/tree/master/instrumentation/http#span-data-policy...

right now folks sometimes use zipkin-aws which includes instrumentation and an xray exporter. I think sqs might be in a different package tho cc @devinsba @llinder

hmm is there an existing issue out to synchronize and/or link the linkerd trace header with another format like X-B3? I might have misspoken about compatibility, which is cool, but...

Hmm so I suppose I might be oversimplifying, but what is actually preventing a trace join plugin? Like a bijection. For example, what would be the risk of continuing a...

yeah I think of these contexts as different, for example, a user ID context being different than a routing rule context being different than tracing context (although they are indeed...

yep can do if no one else in a timeout :P

I'm not sure where the quoted points are from. I'm going to guess they were takeaways from digesting things. https://github.com/openzipkin/b3-propagation#http-encodings prioritizes "b3" over "X-B3-*" indeed that implies ignoring the latter...

thanks for the loopback and appreciate moving this forward. cheers! On Sun, Sep 22, 2019, 4:11 AM Tacalau Daniel Stefan < [email protected]> wrote: > @adriancole I've quoted from your first...

PS many issues I raised are solvable now. This one, however, still requires significant surgery to achieve, sadly undoing some of the value of the other flags.

sorry I dropped the ball on this. let me know if you plan to do a cleanup round or if I should on your behalf!