Hello, I had a similar issue as described in Zipkin not able to collect tracing info thread and therefore I started to use Zipkin’s http collector.
It works fine, but I assume that it is not a preffered way how to connect linkerd to zipkin (because you don’t ship the plugin with linkerd by default). Can you please provide me some more information about performance? Should I take some more time to try to establish communication with use of the scribe collector? We really need to focus on performance in our application… Thanks.
I have one more question. We would like to log more information to zipkin directly from our application (request to DB, etc.). Linkerd forwards
l5d-reqid http header in order to correlate requests across services which we can use. Is it enough to correctly log new child requests to the same trace? I ask, because in trace detail from zipkin, I can see, that there is also a
spanID element which is used to identify parent of the request:
But I cannot find the
spanID in any http header… Do I need to enable the forwarding somehow?