-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Unable to override org.springframework logging levels since 2.1.0.M2 #14310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think this report is much wider than what is happening in practice.
Just to be sure we're taking about the same thing, I assume you mean certain |
Yeah, I mean overriding
|
See #13511 |
The additional output only happens when devtools is present. I think it's due to this change |
Since 2.1.0M2, overriding Spring logging levels in dev mode using
logback-spring.xml
doesn't work. Attaching a project generated with Initializr, withlogback-spring.xml
file (that lowers spring level to WARN) added in resourcesdemo (8).zip. To reproduce:
gradlew bootRun
build.gradle
gradlew bootRun
again and watch spring related log entries disappearOn a side note, I'm not sure if the decision to include these DEBUG logs by default, even in dev mode, was well thought. The result is a lot of unhelpful information in the log. Frankly I would rather leave the DEBUG off by default, as 99% percent of the time I don't need these logs while developing.
Also reported here
The text was updated successfully, but these errors were encountered: