[jboss-jira] [JBoss JIRA] (WFLY-10967) Jaeger Tracing: No sender found

[Harald Wellmann (JIRA)]

Harald Wellmann created WFLY-10967:
--------------------------------------

             Summary: Jaeger Tracing: No sender found
                 Key: WFLY-10967
                 URL: https://issues.jboss.org/browse/WFLY-10967
             Project: WildFly
          Issue Type: Bug
          Components: MP OpenTracing
    Affects Versions: 14.0.0.Final
            Reporter: Harald Wellmann


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

{noformat}
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!
{noformat}

My guess is that the module configuration is not quite correct. After adding the following dependencies, things look better:

module io.jaegertracing.jaeger-core:

{code:xml}
<module name="io.jaegertracing.jaeger-thrift" services="import"/>
{code}

module io.jaegertracing.jaeger-thrift:

{code:xml}
<module name="org.apache.thrift"/>
{code}




--
This message was sent by Atlassian JIRA
(v7.5.0#75005)