Skip to content

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

Closed
docent opened this issue Sep 5, 2018 · 4 comments
Closed

Unable to override org.springframework logging levels since 2.1.0.M2 #14310

docent opened this issue Sep 5, 2018 · 4 comments
Labels
type: bug A general bug
Milestone

Comments

@docent
Copy link

docent commented Sep 5, 2018

Since 2.1.0M2, overriding Spring logging levels in dev mode using logback-spring.xml doesn't work. Attaching a project generated with Initializr, with logback-spring.xml file (that lowers spring level to WARN) added in resources
demo (8).zip. To reproduce:

  • run gradlew bootRun
  • observe log messages
  • revert boot version to 2.1.0.M1 in build.gradle
  • run gradlew bootRun again and watch spring related log entries disappear

On 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

@snicoll
Copy link
Member

snicoll commented Sep 5, 2018

I think this report is much wider than what is happening in practice.

Unable to override logging levels

Just to be sure we're taking about the same thing, I assume you mean certain org.springframework log levels. Overriding of other levels should work fine.

@snicoll snicoll added status: waiting-for-feedback We need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged labels Sep 5, 2018
@docent
Copy link
Author

docent commented Sep 5, 2018

Yeah, I mean overriding org.springframework log levels, e.g.:

<configuration>
    <include resource="org/springframework/boot/logging/logback/base.xml" />
    <logger name="org.springframework" level="warn"/>
</configuration>

@spring-projects-issues spring-projects-issues added status: feedback-provided Feedback has been provided and removed status: waiting-for-feedback We need additional information before we can continue labels Sep 5, 2018
@docent docent changed the title Unable to override logging levels since 2.1.0.M2 Unable to override Spring logging levels since 2.1.0.M2 Sep 5, 2018
@snicoll snicoll changed the title Unable to override Spring logging levels since 2.1.0.M2 Unable to override org.springframework logging levels since 2.1.0.M2 Sep 5, 2018
@snicoll
Copy link
Member

snicoll commented Sep 5, 2018

See #13511

@philwebb philwebb added type: bug A general bug and removed status: feedback-provided Feedback has been provided status: waiting-for-triage An issue we've not yet triaged labels Sep 5, 2018
@philwebb philwebb added this to the 2.1.x milestone Sep 5, 2018
@philwebb
Copy link
Member

philwebb commented Sep 5, 2018

The additional output only happens when devtools is present. I think it's due to this change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

4 participants