Opentelemetry - VertxHttpClient doesn't have his own span

[pjgg]

Describe the bug

I am working with opentelemetry extensions over a Quarkus application, Reactive routes, and vert.x HttpClient:

       <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-opentelemetry</artifactId>
        </dependency>

        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-opentelemetry-exporter-jaeger</artifactId>
        </dependency>

        <dependency>
            <groupId>io.smallrye.reactive</groupId>
            <artifactId>smallrye-mutiny-vertx-web-client</artifactId>
        </dependency>

Based on this doc I expected that If I have an HttpClient behind an endpoint, I will have two spans with the same traceId. The first span represents the endpoint and the second the HttpClient request. But I am getting just one Span per traceId (we are not recording HTTP requests)

You have a reproducer here.

[quarkus-bot]

/cc @kenfinnigan

[kenfinnigan]

Not all usages of OpenTelemetry have been tested/verified at present.

Right now I expect RESTEasy Classic, REST Client, and Reactive Messaging with Kafka to work. Other extensions may "work", but there are no guarantees at present.

In addition, the existing extensions in 1.x will likely change significantly for the 2.x/main stream

[kenfinnigan]

I verified this works with the 2.0 branch.