[logback-user] Verbose status messages, even though no errors or warnings

[Rob W]

Logback starts up verbosely when I use it and I can't figure out why. The documentation says this is supposed to happen if there are errors when it starts up, but there are none. I'm not manually invoking StatusPrinter.print() either. Anyone have any ideas what I might be missing here?

I'm using logback 0.9.16 with slf4j-1.5.8.

The status messages being shown are:

12:07:06,005 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
12:07:06,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/analytics/dist/conf/logback.xml]
12:07:06,108 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender]
12:07:06,112 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
12:07:06,151 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [layout] on top of the object stack.
12:07:06,192 |-INFO in ch.qos.logback.core.FileAppender[FILE] - File property is set to [etl.log]
12:07:06,192 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [FILE] from the object stack
12:07:06,192 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG
12:07:06,192 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[root]
12:07:06,195 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.