You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it seems that multiple servers are annotating / reusing the same spanId now in resulting in strange unwanted behaviour and having the following span in Zipkin.
As reported in the mailing list:
Using the Kamon-ore 1.1.2, Kamon-zipkin 1.0.0
I'm investigating an issue we are having with Kamon tracing and Zipkin;
Following the recommended documentation we have set
kamon.trace.join-remote-parents-with-same-span-id = yes
in our configuration since we are using Zipkin.
But it seems that multiple servers are annotating / reusing the same spanId now in resulting in strange unwanted behaviour and having the following span in Zipkin.
Here is a JSON data snapshot of it:
The text was updated successfully, but these errors were encountered: