Useless log warnings in TracerAutoConfiguration

[Vity01]

If I set opentracing.jaeger.enabled: false which is a standard way how to disable Jaeger in configuration then I get warnings like

Tracer bean is not configured! Switching to ...

Imho these warnings should be set to level DEBUG.

[geoand]

If I set opentracing.jaeger.enabled: false which is a standard way how to disable Jaeger in configuration then I get warnings like

Tracer bean is not configured! Switching to ...

Imho these warnings should be set to level DEBUG.

Hey @Vity01

Can you please post the entire log line?
The reason I am asking is because I am pretty sure that this message isn't produced by this starter

[geoand]

If I set opentracing.jaeger.enabled: false which is a standard way how to disable Jaeger in configuration then I get warnings like

Tracer bean is not configured! Switching to ...

Imho these warnings should be set to level DEBUG.

Hey @Vity01

Can you please post the entire log line?
The reason I am asking is because I am pretty sure that this message isn't produced by this starter

Oops, sorry about the message above, I though the issue was opened on the Jaeger starter :)

[geoand]

I opened #7 to address this.
I have used info instead of warn - I believe info is more appropriate than debug

[Vity01]

Sorry, I should be more specific - I mean this line:

java-spring-tracer-configuration/opentracing-spring-tracer-configuration-starter/src/main/java/io/opentracing/contrib/spring/tracer/configuration/TracerAutoConfiguration.java

Line 64 in ff2ee74

log.warn("Tracer bean is not configured! Switching to " + tracer);

[Vity01]

Thank you for the pretty fast answer&change although I still think the DEBUG is more appropriate in this case.
In the Spring world you usually don't get messages about binded and/or not-binded beans at level INFO.
It's a quite common practice to declare default bean (NoOp in this case) if there is no other instance made by application.

[geoand]

Thank you for the pretty fast answer&change although I still think the DEBUG is more appropriate in this case.
In the Spring world you usually don't get messages about binded and/or not-binded beans at level INFO.
It's a quite common practice to declare default bean (NoOp in this case) if there is no other instance made by application.

You have a point :). PR updated