squakez commented on issue #7801: URL: https://github.com/apache/camel-quarkus/issues/7801#issuecomment-3501909828
Hello. I've made a deep analysis of the problem and I've come up to the conclusion that, this is not a bug on our side. All details in https://issues.apache.org/jira/browse/CAMEL-22648 Let me give here some more explanation. The older `camel-opentelemetry` implementation, was connecting spans (although was affected by inconsistency problems when running in async mode) because, since it was running on the same Thread, it was able to link the current context generated by the vertx library (via the otel agent) to the ones we were using in Camel. The `camel-opentelemetry2` has adopted a different [design](https://github.com/apache/camel/blob/main/proposals/tracing.adoc) in order to prevent those inconsistency issues raised in several Jira tickets. We had discussed this in ML and in a PR around this new design to adopt. Unfortunately the otel agent is the real responsible of this problem as it is not doing the expected job (see more in the jira issue) to propagate downstream via the W3C, which is how the component is expecting to receive the upstream trace (according to [W3C trace context specification](https://www.w3.org/TR/trace-context/)). You can decide if you want to do any patch or what you think it convenient for the project, but I hope I gave enough arguments to accept this not a bug on our side (it's indeed a bug on the agent). FYI, I am already trying to fix this problem on the agent and will let you know how it goes, as, in such case should clear this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
