Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.4.1
-
None
-
Unknown
Description
When using Camel's opentracing implementation alongside other tracers e.g. anything from https://github.com/opentracing-contrib traces do not link up nicely.
It appears that although Camel has the ActiveSpanManager which correctly tracks the span stack locally the implementation doesn't activate spans in the global tracer.
This means that when viewing spans you get broken traces for events in the same distributed transaction e.g.
from("direct:personInJsonToDb")
.unmarshal(jsonDataFormat)
.bean(DatabaseClient.class, "insert");
You can see 2 root traces in the attached image.
It's possible to workaround this by intercepting and activating 'manually' but that doesn't seem correct.
I think we should be activating in the global tracer when we activate locally.
