[logback-user] Logging to stderr and stdout

Steve Ramage vcolo at sjrx.net
Sun Oct 21 00:30:11 CEST 2012

I had a question about the conventions of logging. We have an application scientific in nature, and basically it runs some process for some amount of time, and then finishes with it's output. All output in the program is driven by logback, and we generally hide the complexity of logback from our users, and support very limited configuration as needed.


One issue is where error and warning messages should go for users.


One argument is that they should go to stderr.  stdout should have INFO, DEBUG, and TRACE. There doesn't seem to be an easy way to do this in logback.


Another argument is that they should go to stderr. stdout should also have them, but also INFO, DEBUG, and TRACE. If the user is running directly then both get spammed together.


A final option is they should all go to stdout, as these are all log messages, and there is no need to split them


Now this isn't so much a religious argument,  we are just more wondering what the conventions were, as we would like to follow them as much possible.




Steve Ramage

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20121020/947684de/attachment.html>

More information about the Logback-user mailing list