-
Bug
-
Resolution: Duplicate
-
Major
-
14.0.0.Final
-
None
I'm not really sure what the intended behaviour is, but is seems that MicroProfile OpenTracing does not work out of the box.
When deploying a JAX-RS + CDI application, I get the following warning
16:37:49,023 WARN [io.jaegertracing.internal.senders.SenderResolver] (ServerService Thread Pool -- 73) No suitable sender found. Using NoopSender, meaning that data will not be sent anywhere!
My guess is that the module configuration is not quite correct. After adding the following dependencies, things look better:
module io.jaegertracing.jaeger-core:
<module name="io.jaegertracing.jaeger-thrift" services="import"/>
module io.jaegertracing.jaeger-thrift:
<module name="org.apache.thrift"/>
- duplicates
-
WFLY-10961 MP-OpenTracing Jaeger's can't see a concrete sender
- Closed