-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Logging
Ayitaka edited this page Aug 12, 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 'warn' (default is 'info'). The Log level 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 to work properly.
LOG_LEVEL options are: "trace", "debug", "info", "warn", "error" or "off".
docker run -d --name bitwarden \
...
-e LOG_LEVEL=warn -e EXTENDED_LOGGING=true \
...- Which container image to use
- Starting a container
- Using Docker Compose
- Using Podman
- Updating the vaultwarden image
- Overview
- Enabling admin page
- SMTP configuration
- Disable registration of new users
- Disable invitations
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Enabling SSO support using OpenId Connect
- Other configuration
- Using the MariaDB (MySQL) Backend
- Using the PostgreSQL Backend
- Running without WAL enabled
- Migrating from MariaDB (MySQL) to SQLite
- Hardening Guide
- Password hint display
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Fail2Ban Setup
- Fail2Ban + ModSecurity + Traefik + Docker
- Translating the email templates
- Translating admin page
- Customize Vaultwarden CSS
- Using custom website icons
- Disabling or overriding the Vault interface hosting
- Building binary
- Building your own docker image
- Git hooks
- Differences from the upstream API implementation