Adding the LogDigger Appender to your Log4j configuration is an optional, but recommended step.
The servlet filter will look for the LogDigger Appender in the runtime configuration of Log4j, and if the appender is not found, will add it to the ROOT logger. In this case the LogDigger Appender may log events either from the underlying framework, or from bundled libraries, which may not be of interest. With an explicit configuration, developers control which log messages they receive.
log4j.rootLogger=ERROR, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d %p [%c] - %m%n
log4j.appender.LOGDIGGER=com.logdigger.connector.log4j.LogDiggerAppender
#log4j.appender.LOGDIGGER.allowLogLevelChange=false
log4j.logger.foo.bar=INFO, LOGDIGGER
By setting the appender parameter allowLogLevelChange, you can control whether the user can change the logging level (scoped to request execution).