[jira] [Resolved] (CAMEL-15260) OpenTracing - camel tracer appears not to activate spans in global tracer

["Andrea Cosentino (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-15260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Cosentino resolved CAMEL-15260.
--------------------------------------
    Resolution: Fixed

> OpenTracing - camel tracer appears not to activate spans in global tracer
> -------------------------------------------------------------------------
>
>                 Key: CAMEL-15260
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15260
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-opentracing
>    Affects Versions: 3.4.1
>            Reporter: Matt Robbins
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 3.5.0, 3.4.2
>
>         Attachments: Screenshot from 2020-06-30 12-45-08.png
>
>
> 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.
> {code}
>         from("direct:personInJsonToDb")
>                 .unmarshal(jsonDataFormat)
>                 .bean(DatabaseClient.class, "insert");
> {code}
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)