There are some ways to get all the log traces to the "logs tab": Add one additional step into your docker build strategy to replace the logging.properties from $JWS_HOME/conf with the one attached. or Add the attached logging.properties file into a directory that you want and reference it via the LOGGING_CONFIG environment variable into your Deployment Configuration, like: ~~~ LOGGING_CONFIG="-Djava.util.logging.config.file=/<custom directory>/logging.properties" ~~~ or Add one additional step into your docker build strategy to remove the logging.properties from $JWS_HOME/conf to be able to use $JAVA_HOME/jre/lib/logging.properties as default. Note: this will change a bit the logging format as before, because the logging.properties from the jdk uses a different formatter than juli. or Set the LOGGING_CONFIG environment variable into your Deployment Configuration to use the jdk properties, like: ~~~ LOGGING_CONFIG="-Djava.util.logging.config.file=$JAVA_HOME/jre/lib/logging.properties" ~~~ Note: this also will change a bit the logging format as before, because the logging.properties from the jdk uses a different formatter than juli. There are more options, like defining a LOGGING_MANAGER with empty -Djava.util.logging.manager to generate an exception loading the juli handlers (or setting it to java.util.logging.ConsoleHandler and provide other properties file) but you will see errors on stacktrace, this way is not recommended. Finally, note for the envvar use cases, you can also set the envvars to the dockerfile instead on deployment config, if you want.