You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/10/23 07:15:00 UTC
[jira] [Resolved] (CAMEL-15710) OpenTracingTracer does not activate
created span
[ https://issues.apache.org/jira/browse/CAMEL-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-15710.
---------------------------------
Resolution: Fixed
Thanks for reporting and the PRs
> OpenTracingTracer does not activate created span
> ------------------------------------------------
>
> Key: CAMEL-15710
> URL: https://issues.apache.org/jira/browse/CAMEL-15710
> Project: Camel
> Issue Type: Bug
> Components: camel-opentracing
> Affects Versions: 3.4.1
> Reporter: Bogdan Ilchyshyn
> Priority: Major
> Fix For: 3.4.5, 3.7.0
>
>
> {{OpenTracingTracer}} does not activate the span it creates in {{onExchangeBegin}} (i.e. does not invoke {{tracer.activateSpan}}). Whenever there is processor invoked down the route, and this processor code is instrumented for OpenTracing (for instance, JDBC calls via {{opentracing-contrib/java-spring-cloud}}), the newly created spans are not aware about a trace being active and start a new trace. This leads to all such spans being detached from the route trace. It is a major issue for Camel routes observability via OpenTracing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)