From 0d38331b25c813f64b143923ea9e73bb088032ba Mon Sep 17 00:00:00 2001 From: Ayitaka Date: Mon, 12 Aug 2019 06:02:31 -0700 Subject: [PATCH] The way to properly set log level was changed. --- Logging.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Logging.md b/Logging.md index 721f6d3..eb743d8 100644 --- a/Logging.md +++ b/Logging.md @@ -13,11 +13,13 @@ Note that if you're using the docker image, you'll most likely want to use a fil # Change the log level -To reduce the amount of log messages, you can set the log level to 'critical' (default is 'normal') and disable the extended logging (enabled by default). The [Log level](https://api.rocket.rs/v0.3/rocket/config/enum.LoggingLevel.html) can be adjusted with the environment variable `ROCKET_LOG`. Extended logging can be deactivated by setting the environment variable `EXTENDED_LOGGING` to 'false'. Be advised, disabling `EXTENDED_LOGGING` will stop the log file from being written to. +To reduce the amount of log messages, you can set the log level to 'warn' (default is 'info'). The [Log level](https://docs.rs/log/0.4.7/log/enum.Level.html#variants) can be adjusted with the environment variable `LOG_LEVEL` while also setting `EXTENDED_LOGGING=true`. NOTE: Using the log level "warn" still allows [Fail2Ban](https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup) to work properly. + +`LOG_LEVEL` options are: "trace", "debug", "info", "warn", "error" or "off". ```sh docker run -d --name bitwarden \ ... - -e ROCKET_LOG=critical -e EXTENDED_LOGGING=false \ + -e LOG_LEVEL=warn -e EXTENDED_LOGGING=true \ ... ``` \ No newline at end of file