Paulo Casaes

Did some more testing. Looks like that started happening on 0.69.0. On 0.68.0 it's working fine.

Looks like the issue is in this line https://github.com/DataDog/dd-trace-java/blob/6e4d65ff54b79fd5af196f4846b9f3670661cf39/dd-java-agent/instrumentation/vertx-web-3.4/src/main/java8/datadog/trace/instrumentation/vertx_3_4/server/VertxRouterDecorator.java#L52 According to the Vertx docs Route#getPath returns the path **prefix** (if any) for this route https://vertx.io/docs/apidocs/io/vertx/ext/web/Route.html#getPath-- I suppose you could use...

> I demonstrated that your suggestion to use routingContext.request().path() would be problematic because it returns the original URL That makes sense. If the root path _quarkus.http.root-path_ property is not set...

Going back to having the property _quarkus.http.root-path_ set, if I disable vertx instrumentation _-Ddd.integration.vertx-3.4.enabled=false_ then it works! It looks like if the current route's path is null or if Vertx...

Seeing the same issue on keycloak 20 with agent 1.10.1

We were able to improve things a bit by enabling these flags https://github.com/DataDog/dd-trace-java/issues/5042

I've seen this same issue with the confluent protobuf deser (same version >= 3.5.0). The debugger is showing that `dead-letter-queue.value.serializer` is set to some synthetic class based off of the...

setting the dead letter value serializer is a viable workaround ``` dead-letter-queue.value.serializer=io.confluent.kafka.serializers.protobuf.KafkaProtobufSerializer ```

My setup is similar. A proto file with generated java classes in a separate module. I'll try adding the jandex index.

Configuring jandex made no difference. I even moved the proto files into the application module, no joy. Disabling `QUARKUS_REACTIVE_MESSAGING_KAFKA_SERIALIZER_GENERATION_ENABLED` did resolve it