Hello everyone,
we recently started to use linkerd and so far it was a rather pleasent experience. Unfortunately since we started using linkerd we encountered problems with our request tracing. We are using opentracing (with stackdriver as our backend) in all our services and propagate the span ids etc. via the default opentracing headers. Unfortunately these headers seem to be lost since our services are creating now new root spans on every request.
In the debugging output I also can’t see the opentracing headers. On the other hand we transport request context in our headers an all these header keys start with ‘X-’ (in contrast to the opentracing headers). These seem to be available.
How does linkerd handle custom headers? Is it filtering everything not starting with ‘X-’?
Generally I think it would be great if linkerd would have support for opentracing and use the tracing ids from the opentracing headers.
Our setup is rather straight forward. Kubernetes with linkerd as daemon-set and and requests are routed from service -> linkerd -> linkerd -> target-service.
Routing etc. works as expected.
Thanks in advance for the help.
