jamesnetherton opened a new issue, #8277: URL: https://github.com/apache/camel-quarkus/issues/8277
### Bug description I discovered this by switching the [Observability example project](https://github.com/apache/camel-quarkus-examples/tree/main/observability) from `camel-quarkus-http` to `camel-quarkus-vertx-http`. Here's a typical view of how tracing looks. All 10 spans should be connected together, but they are split: <img width="500" height="500" alt="vertx-http-traces" src="https://github.com/user-attachments/assets/4c023679-8e36-4377-92b8-3ba72d54551d"; /> I think it's caused when the Vert.x HTTP Client creates its own internal spans. When tracing is suppressed on the client, then all of the Camel route spans are connected properly. I tested with a standalone `camel-main` application and this issue does not occur when the Otel agent is used. The workaround will be to disable internal tracing for the HTTP client. You loose a span for the request but we still have the `vertx-http` endpoint span, which contains mostly identical info. -- 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]
