5

According to the Spring Boot documentation, it is possible to set the logging level of multiple logging framework (jul, slf4j, etc.) just by using the Spring Boot Logging Starter and setting appropriate logging.level in application properties. Everything works fine except that the library I use is logging with jul and log level Level.FINER. However, Level.INFO is properly logged.

I set level in application.properties to:

logging.level.=TRACE

which should log everything according to SLF4JBridgeHandler.

Am I something missing or is it a problem of logback (used by the starter) rather my misunderstanding?

Improve this question
6
  • logging.level. doesn't match anything. I would expect logging.level.* to work. Else specify the FQN or atl east base package. Commented Aug 19, 2014 at 8:30
  • 1
    logging.level.ROOT would set the default logger level. Commented Aug 19, 2014 at 11:15
  • M. Deinum sorry it is just typo @Dave I also tried it but it doesn't log from that library which is using JUL either... I also tried to use the logback.xml setting with same result. Is it possible that the logback - jul bridge is not set properly I see logback-core-1.1.2.jar and logback-classic-1.1.2.jar but not the bridge jar Commented Aug 21, 2014 at 15:28
  • You definitely need to bridge, but if you use spring-boot-starter-* for your dependencies that should be there. Commented Aug 21, 2014 at 18:12
  • I have this dependency in my build.gradle compile 'org.springframework.boot:spring-boot-starter-logging' so is there any difference to spring-boot-starter-*? My Spring Boot version is 1.1.4.RELEASE Commented Aug 22, 2014 at 6:55

2 Answers 2

Reset to default
1

Please see my related answer: https://stackoverflow.com/a/33770877/3004042

In short, use Spring Boot version 1.3.0 with Logback.

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
@JeenBroekstra What do you mean? This is the answer. The user can solve the problem with Spring Boot version 1.3.0 and logback, since Spring Boot 1.3.0 added a feature related to this question.
apologies, you're right. I misread and thought you only provided a link, in which case it should have been a comment, not an answer. I overlooked the last bit.
@NathanHughes No, I'll wait a few days before accepting my own answer for better answer than mine. But meanwhile others can be helped by this answer since this answer solves the problem anyway. Regarding the close vote, I think they are two separate questions those happened to have the same cause and therefore the same answer. So it's better to be two separate ones.
0

SLF4JBridgeHandler only receives LogRecord from enabled levels on jul Loggers (this fact is hidden in the javadoc of the install method)

As the default JUL configuration only logs INFO or higher level, the bridge doesn't receive FINE/FINER/FINEST levels.

In order to test this you can force the level of the root jul logger like this : 

LogManager.getLogManager().getLogger("").setLevel(Level.FINE);

(or configure explicitly a custom logging.properties with .level=FINE on your JVM)

This configuration must be completed with slf4j level configuration (via logback.xml or logging.level.xxxxxx properties in application.properties)

( Please note, you should be more specific in your jul production configuration as slf4j documentation warns about performance impact of "jul enabled" but "slf4j disabled" logs )

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.