[jboss-jira] [JBoss JIRA] (WFLY-13070) Use NoopTracer by default
Simon Priadka (Jira)
issues at jboss.org
Thu Feb 6 10:48:00 EST 2020
[ https://issues.redhat.com/browse/WFLY-13070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Priadka moved JBEAP-18676 to WFLY-13070:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13070 (was: JBEAP-18676)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: MP Config
MP OpenTracing
(was: MP Config)
(was: MP OpenTracing)
Affects Version/s: 19.0.0.Beta2
(was: 7.3.0.GA)
> Use NoopTracer by default
> -------------------------
>
> Key: WFLY-13070
> URL: https://issues.redhat.com/browse/WFLY-13070
> Project: WildFly
> Issue Type: Bug
> Components: MP Config, MP OpenTracing
> Affects Versions: 19.0.0.Beta2
> Reporter: Simon Priadka
> Assignee: Jeff Mesnil
> Priority: Major
>
> When deploying an [app-client quickstart|https://github.com/wildfly/quickstart/tree/master/app-client], following lines are present in the server log:
> {code}
> 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.
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list