Hi!
As far as I know, Ignite does not support Zipkin trace propagation out of
the box, unlike Spring Cloud. Hence request handler in {{rest-http}} loses
tracing-context-specific headers (see [1]) sent with request and the span
gets broken into two parts. This can be worked around by
replacing {{re
Hi,
As far as I remember zipkin defines tracing units in a current thread
of execution. I cannot say for sure what goes wrong in your case. But
it might be that traced execution on ser3 side switches from one
thread to another and you see 2 units as a result.
чт, 14 мар. 2019 г. в 02:09, Aditya K
Hi Team,
I was using ignite as dependecy in our application and was able to trace end to
end trace microservice calls.
Then, to let ignite handle our services in compute task, we removed all
spring-boot dependencies and created task for each service we had in our
microservice.
The issue we ar
