From 7552840f2741f9529f4ef50199358b16ab0980e7 Mon Sep 17 00:00:00 2001 From: Jeremy Finzel Date: Tue, 29 Sep 2020 08:45:15 -0500 Subject: [PATCH] DBZ-2541 Add docs about new CONNECT_LOG4J environment variables --- .../modules/logging/proc-configuring-log-level-docker.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/documentation/modules/ROOT/partials/modules/logging/proc-configuring-log-level-docker.adoc b/documentation/modules/ROOT/partials/modules/logging/proc-configuring-log-level-docker.adoc index 624cb8bf7..48d9d0d3e 100644 --- a/documentation/modules/ROOT/partials/modules/logging/proc-configuring-log-level-docker.adoc +++ b/documentation/modules/ROOT/partials/modules/logging/proc-configuring-log-level-docker.adoc @@ -11,6 +11,12 @@ When you start the container, set this environment variable to one of the log levels (for example, `-e LOG_LEVEL=DEBUG`), and all of the code within the container will use that log level. +There is also an option to override other log4j properties. If you want to configure `log4j.rootLogger` +differently, then use the environment variable `CONNECT_LOG4J_LOGGERS`. For example to log only to stdout +(without `appender`), you can use `CONNECT_LOG4J_LOGGERS=INFO, stdout`. You can also set other supported +log4j environment variables with the CONNECT_LOG4J prefix, which will be mapped to properties in the `log4j.properties` +file by removing the `CONNECT_` prefix, lowercasing all characters, and converting all '_' characters to '.'. + If you need more control over the logging configuration, create a new container image that is based on ours, except that in your `Dockerfile`, copy your own `log4j.properties` file into the image.