[jboss-jira] [JBoss JIRA] (WFLY-10919) INFO message Initialized tracer=JaegerTracer is too verbose

[Juraci Paixão Kröhling (Jira)]

    [ https://issues.jboss.org/browse/WFLY-10919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660758#comment-13660758 ] 

Juraci Paixão Kröhling commented on WFLY-10919:
-----------------------------------------------

I had a discussion about this with upstream at the time our QE reported that this was an issue, and their reasoning is that:

> bootstrap can be verbose because it allows for easy checks on what the actual configuration of the tracer is on production

I tend to agree with that, especially considering the usual consumers of the library but I can also understand that WildFly should be restrictive on what's logged during bootstrap, as quite a few things are happening.

Given that, I believe the best (only?) solution is indeed to set the logger to record messages with a minimal level of WARN for the `io.jaegertracing.Configuration` class.

For reference, here are a couple of GitHub resources on this:
https://github.com/jaegertracing/jaeger-client-java/pull/531
https://github.com/jaegertracing/jaeger-client-java/issues/79


> INFO message Initialized tracer=JaegerTracer is too verbose
> -----------------------------------------------------------
>
>                 Key: WFLY-10919
>                 URL: https://issues.jboss.org/browse/WFLY-10919
>             Project: WildFly
>          Issue Type: Bug
>          Components: MP OpenTracing
>    Affects Versions: 14.0.0.Beta2
>            Reporter: Jan Stourac
>            Assignee: Juraci Paixão Kröhling
>            Priority: Major
>
> Following log message is logged during the deploy operation of a deployment:
> {code}
> 10:52:11,703 INFO  [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer=JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> This information is too verbose for INFO level. I propose to do one of following:
> # Remove this log message from INFO level - note that very similar message is also logged on DEBUG level:
> {code}
> 10:52:11,714 DEBUG [org.wildfly.microprofile.opentracing.smallrye] (ServerService Thread Pool -- 72) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> # Simplify the log message on INFO level to something simple, like:
> {code}
> 10:52:11,703 INFO  [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer for service helloworld-rs.war
> {code}
> This issue is a followup of a WFLY-10904.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)