-
Feature
-
Resolution: Duplicate
-
Major
-
None
-
fuse-7.0
-
0
-
0%
-
-
Todo
The current Zipkin instrumentation generates tracing IDs during client requests (in com.github.kristofa.brave.ClientTracer.startNewSpan()). However, it does not do so for server requests (see ZipkinTracer.ZipkinRoutePolicy.onExchangeBegin()). This means that if the client does not supply its own tracing headers, nothing will be traced until a client request is made from within Camel.
Upstream issue: https://issues.apache.org/jira/browse/CAMEL-12109
- duplicates
-
ENTESB-9301 CAMEL-12109: camel-zipkin - Generate tracing identifiers on exchange begin if they do not exist
- Closed
- relates to
-
ENTESB-9301 CAMEL-12109: camel-zipkin - Generate tracing identifiers on exchange begin if they do not exist
- Closed
-
ENTESB-9305 camel-zipkin - Add support for easy enabling of logging integration
- Closed