Redirect log output for commands other than "server" about dropwizard HOT 2 CLOSED

Hi @JamesBoon. The config overrides only accept simple string values and arrays of strings. Hence, they cannot be used to override the whole appenders object.

The filter factories also work for other commands since they reside in dropwizard-logging and don't depend on any logic related to the server command. The docs only provide an example for a FilterFactory<IAccessEvent> that is indeed only related to request logging within the server command. To obtain a filter factory for a "normal" appender rather than a request log appender, you'll need to provide a FilterFactory<ILoggingEvent>.

I think the simplest solution for your use case is to use environment variables for the logging levels of the appenders. Then you can provide an environment variable with the value OFF to disable logging for the other appenders.

from dropwizard.

Thank you @zUniQueX, that was the hint I needed!

If anyone else needs it:

appenders:
  - type: console
    threshold: ${DW_LOG_THRESHOLD_CONSOLE:-OFF}
    # ...
  - type: file
    threshold: ${DW_LOG_THRESHOLD_FILE:-INFO}
    # ...

This way, the console logger is OFF by default, but can be switched on by setting the environment variable DW_LOG_THRESHOLD_CONSOLE to any log level like e.g. INFO.
The file logger is on by default and can be switched off by setting DW_LOG_THRESHOLD_FILE=OFF.

Just before anybody asks, yes the same thing can be achieved via passing system properties. But this should only be used if the number and order of the log appenders is always fixed!
-Ddw.logging.appenders[0].threshold=INFO -Ddw.logging.appenders[1].threshold=OFF

from dropwizard.