From d24082192f9e3c6dc468166df1b199a786aa451c Mon Sep 17 00:00:00 2001 From: Jonghee Son Date: Sat, 11 Jun 2022 16:03:13 +0900 Subject: [PATCH] Added USE_SYSLOG environment variable. --- Logging.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/Logging.md b/Logging.md index 557d98e..d0b9786 100644 --- a/Logging.md +++ b/Logging.md @@ -1,4 +1,4 @@ -vaultwarden logs only to [standard output](https://en.wikipedia.org/wiki/Standard_streams#Standard_output_(stdout)) (stdout) by default. You can also configure it to log to a file. +vaultwarden logs only to [standard output](https://en.wikipedia.org/wiki/Standard_streams#Standard_output_(stdout)) (stdout) by default. You can also configure it to log to a file or Syslog. ## Logging to a file @@ -13,6 +13,19 @@ docker run -d --name vaultwarden \ When this environment variable is set, log messages will be logged to both stdout and the log file. If you're running in Docker, you'll most likely want to use a file path that is mounted from the Docker host (such as the `data` folder); otherwise, your log file will be lost (or at least hard to find) if the container is restarted or removed. +## Logging to Syslog + +You can use Syslog with the `USE_SYSLOG` environment variable while alse setting `EXTENDED_LOGGING=true`: + +```sh +docker run -d --name vaultwarden \ +... + -e USE_SYSLOG=true -e EXTENDED_LOGGING=true \ +... +``` + +When this environment variable is set, log messages will be logged to both stdout and Syslog. + ## Changing the log level 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" or "error" still allows [Fail2Ban](https://github.com/dani-garcia/vaultwarden/wiki/Fail2Ban-Setup) to work properly.