You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2021/09/03 09:03:00 UTC
[jira] [Commented] (CAMEL-16859) Opentelemetry > tracing
information lost between incoming and outgoing message
(opentelemetry-java-instrumentation)
[ https://issues.apache.org/jira/browse/CAMEL-16859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409387#comment-17409387 ]
James Netherton commented on CAMEL-16859:
-----------------------------------------
This isn't related to camel-opentelemetry component. The mentioned example project doesn't use it. Rather it's related to the OpenTelemetry Java Agent.
I had a brief look at it. I think the issue is thread related. When all of the kafka producer / consumer parts are initiated from separate threads (as they are in Camel), then you end up with the split traces for the topic produce / consume parts. It's pretty simple to replicate the problem in a simple standalone Kafka Java app without Camel.
FWIW, I tried the same style of app with Camel Quarkus and the trace & spans are recorded as expected under a single trace. Quarkus doesn't need the Java agent, so that makes me think maybe that's where the root cause of the problem is.
> Opentelemetry > tracing information lost between incoming and outgoing message (opentelemetry-java-instrumentation)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-16859
> URL: https://issues.apache.org/jira/browse/CAMEL-16859
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka, camel-opentelemetry
> Affects Versions: 3.11.0
> Reporter: Matthieu Ghilain
> Priority: Major
>
> I am using Camel 3.11.0 with Spring boot and opentelemetry-java-instrumentation java agent version 1.3.1 to implement distributed tracing across my microservices.
> The trace id is not propagated between the input and output message. A new trace id is created for outgoing messages and therefore correlation is lost.
> If you need additional information to investigate don't hesitate to ask.
> (see discussion here -> [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/OpenTelemetry.20-.20Trace.20Messages])
>
> Sample project -> https://github.com/ghilainm/camel-spring-boot-showcase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)