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

MicroProfile Opentracing data not sent to the tracer

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Blocker Blocker
    • None
    • 28.0.0.Beta1
    • MP OpenTracing
    • None
    • Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial, User Experience
    • ---
    • ---

      A MicroProfile OpenTracing test is failing against WildFly since https://issues.redhat.com/browse/WFLY-16238 was implemented.

      No documentation was found about the above mentioned change, so this should be fixed, but eventually the root cause was identified in WildflySenderFactory which is checking whether an endpoint or a host name + port has been set explicitly for the tracer.

      The first thing then should be to fix the community documentation, see https://issues.redhat.com/browse/WFLY-16238?focusedCommentId=21622056&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21622056.
      The related Quickstart is an example of misleading documentation, see https://github.com/wildfly/quickstart/tree/main/microprofile-opentracing/#implicit-tracing-of-rest-resources

      That being said, though, even when setting the endpoint explicitly and a concrete sender is created, traces for the expected deployment service are not found in Jaeger, and this is a regression against WildFly 27, hence the Blocker priority.

            jaslee@redhat.com Jason Lee
            fburzigo Fabio Burzigotti
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: