Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10967

Jaeger Tracing: No sender found

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • 15.0.0.Final
    • 14.0.0.Final
    • MP OpenTracing
    • None

    Description

      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"/>

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. WFLY-10961 MP-OpenTracing Jaeger's can't see a concrete sender

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              hwellmann.de Harald Wellmann (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: