The logging framework used in the DuraCloud application is SLF4J with the LogBack implementation statically bound at runtime.
See the LogBack website for a detailed description of the configuration options.
The application also contains bridges for both Log4J and Commons-Logging which translates any underlying, dependency libraries which are configured to write to these frameworks into the SLF4J API. The effect is that all logging is channeled through the SLF4J configuration.
- By default, if no configuration file is found by LogBack, the logging level is set to "DEBUG" and the appender is set to "STDOUT"
When starting any DuraCloud application, a LogBack configuration file may be specified by using the following system variable
- Additionally, LogBack will use the file named "logback.xml" found at the top of the classpath for configuration
- Notes on the above logback.xml file
- on line 4, the attribute "debug" applies to displaying configuration information when LogBack starts up if set to "true"
- on line 4, the attribute "scan" configures LogBack to re-read the given logback.xml every 60 seconds (by default) for updates
- on line 26, the attribute "additivity" configures the given logger to inherit the configuration of the parent logger, in this case, the root logger
- on line 26, if the "additivity" attribute were set to "true", all "DURACLOUD" log output would also log to "STDOUT"