Spring Boot should make it easy to configure logging without needing to learn the underlying logging tools.

[berlin-ab]

Ideally, logging configuration would live in application.yml along with all other externalized configuration.

Currently, developers need to read and understand Logback, SLF4J, or Commons Logging documentation and then create a configuration file for one of these underlying systems. Spring Boot should provide some configuration abstraction over these services.

[philwebb]

Similar to DropWizard?

https://dropwizard.github.io/dropwizard/manual/core.html#id4

[dsyer]

We already support a "debug" flag in external configuration. I think we can probably do some more along those lines, and probably individual logging levels per package/class. But (hopefully obviously) we'd probably never be able to support all the features of even one of the logging systems.

[berlin-ab]

We configured:

• format and log level for all of our projects
• log level for dependent projects

[berlin-ab]

Also, we've been using Java Service Wrapper to start up the application in production. So we allow our Spring Boot applications write to standard out and have JSW handle log rotation, etc.

[philwebb]

@berlin-ab See #519 for the service wrapper feature request. If you have any comments about your experiences with JSW, please add them to that bug.

[philwebb]

@berlin-ab Also, could you share your logging configuration? Perhaps we should review our defaults.

[berlin-ab]

@philwebb I've sent you our logging configuration via email. Also, I posted to #519 about Java Service Wrapper. I like your DropWizard example, although we don't need/want all of the features their configuration provides. As stated before, we prefer to output to standard out and let the service wrapper be concerned with how to preserve logs.

[btiernay]

Would be nice to have just one configuration file. I enjoyed this about DW. Managing a Java project is synonymous with juggling config files, or so it seems ;)