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

WARN about using NoopTracer by default

    XMLWordPrintable

Details

    • Hide

      1. Install WF and launch it
      2 . Deploy app-client
      3. Observe logs

      Show
      1. Install WF and launch it 2 . Deploy app-client 3. Observe logs

    Description

      When deploying an app-client quickstart, following lines are present in the server log:

      16:24:38,057 WARN  [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-8) WFLYTRAC0003: Could not determine the service name and can't therefore use Jaeger Tracer. Using NoopTracer.
16:24:38,058 WARN  [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-2) WFLYTRAC0003: Could not determine the service name and can't therefore use Jaeger Tracer. Using NoopTracer.

      As I haven't done anything to the MP configuration, I don't think seeing a WARN message about failing to create a resource I have very little or no interest in, should be present in the logs.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18675 WARN about using NoopTracer by default

          • 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

              ehugonne1@redhat.com Emmanuel Hugonnet
              rhn-engineering-spriadka Simon Priadka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: