You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/07/07 08:31:50 UTC

[GitHub] [camel-quarkus] jamesnetherton opened a new issue #2884: Investigate better integration with `@Traced` beans

jamesnetherton opened a new issue #2884:
URL: https://github.com/apache/camel-quarkus/issues/2884


   Prompted by a [question](https://lists.apache.org/thread.html/r93a94bc56e3d55133cb2c150b24538424728cb1ec8fd82ff2fd8a88e%40%3Cusers.camel.apache.org%3E) on the Camel users mailing list.
   
   If you use `@Traced` beans in a Camel route, the parent Span is not propagated to the bean method invocations. So you end up with separate disconnected traces. I outlined a workaround in the mailing list thread, maybe there's a better way of doing things.


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org