Mutiny & Opentelemetry

[ferencbeutel4711]

Hello there,

we are currently trying to implement opentelemetry using the quarkus opentelemetry package. We are using Mutiny in a lot of places in our application. Now we are facing the following issue:
Every time we are using Uni/Multi in our Code, the tracing information is wrong. There are 2 main issues:

• The recorded duration takes only the synchronous part of the method into account
• methods called inside of the Uni/Multi, for example transformation or invoke blocks, are not correlated to the parent span

We think these issues are there due to the threading nature of Mutiny and that the opentelemetry context is lost during those thread switches. Do you have any idea on compatibility? I know there is a smallrye-opentelemetry package here on github, however it is labeled as a POC so not sure what the current situation is

[jponge]

Hello, this issue should go to Quarkus.