-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Logging
M2Shawning edited this page Apr 27, 2019
·
9 revisions
Logging to a file is supported as of 1.5.0. You can specify the path to the log file with the LOG_FILE
environment variable:
docker run -d --name bitwarden \
...
-e LOG_FILE=/data/bitwarden.log \
...
Note that if you're using the docker image, you'll most likely want to use a file path that is mounted from the host OS (such as the data folder).
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 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.
docker run -d --name bitwarden \
...
-e ROCKET_LOG=critical -e EXTENDED_LOGGING=false \
...
- Which container image to use
- Starting a container
- Updating the vaultwarden image
- Using Docker Compose
- Using Podman
- Building your own docker image
- Building binary
- Pre-built binaries
- Third-party packages
- Deployment examples
- Proxy examples
- Logrotate example
- Overview
- Disable registration of new users
- Disable invitations
- Enabling admin page
- Disable the admin token
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Changing persistent data location
- Changing the API request size limit
- Changing the number of workers
- SMTP configuration
- Translating the email templates
- Password hint display
- Disabling or overriding the Vault interface hosting
- Logging
- Creating a systemd service
- Syncing users from LDAP
- Using an alternate base dir (subdir/subpath)
- Other configuration