jamesnetherton opened a new issue, #8280:
URL: https://github.com/apache/camel-quarkus/issues/8280
Given a route like:
```java
from("vertx-websocket:/hello")
.to("direct:logGreeting");
from("direct:logGreeting")
.log("Greeting: ${body}");
from("timer:tick?period=10000?repeatCount=1")
.setBody().constant("Hello World")
.to("vertx-websocket:/hello");
```
The trace span hierarchy result is:
<img width="800" height="800" alt="Vert.x WebSocket Traces"
src="https://github.com/user-attachments/assets/5dae1123-6d36-467d-a6b9-29c2d85006c9";
/>
In some regards, this is expected. The nature / lifecycle of the WebSocket
mean you'll get:
1. A span generated from the Vert.x HTTP server for the initial WS upgrade
2. Separate spans generated for the `timer` consumer and the trigger of the
`vertx-websocket` producer
3. Separate spans for the `vertx-websocket` consumer and the `direct`
producer
The traces are separated because there is no easy way of associating the
full end-to-end routing with the original HTTP request.
We could perhaps see if it's possible to add an otel span 'link' back to the
initial HTTP span so that the overall trace picture makes better sense.
This is similar to how `quarkus-websockets-next` tracing works.
Or remove / suppress the span generated from the Vert.x HTTP server for the
initial WS upgrade entirely.
--
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]
