9 Logging

Jonghee Son edited this page 2022-06-11 16:03:13 +09:00

Table of Contents

• Logging to a file
• Logging to Syslog
• Changing the log level
• Viewing logs

vaultwarden logs only to standard output (stdout) by default. You can also configure it to log to a file or Syslog.

Logging to a file

Logging to a file is supported as of version 1.5.0. You can specify the path to the log file with the LOG_FILE environment variable:

docker run -d --name vaultwarden \
...
  -e LOG_FILE=/data/vaultwarden.log \
...

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:

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 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 vaultwarden \
...
  -e LOG_LEVEL=warn -e EXTENDED_LOGGING=true \
...

Viewing logs

If running in Docker: docker logs <container-name>

If running via systemd: journalctl -u vaultwarden.service (or whatever your service is named)

Otherwise, check where standard output is being redirected, or set the LOG_FILE environment variable and view that file.

FAQs

1. FAQs
2. Audits

Container Image Usage

1. Which container image to use
2. Starting a container
3. Updating the vaultwarden image
4. Using Docker Compose
5. Using Podman

Deployment

1. Building your own docker image
2. Building binary
3. Pre-built binaries
4. Third-party packages
5. Deployment examples
6. Proxy examples
7. Logrotate example

HTTPS

1. Enabling HTTPS
2. Running a private vaultwarden instance with Let's Encrypt certs

Configuration

1. Overview
2. Disable registration of new users
3. Disable invitations
4. Enabling admin page
5. Disable the admin token
6. Enabling WebSocket notifications
7. Enabling Mobile Client push notification
8. Enabling U2F and FIDO2 WebAuthn authentication
9. Enabling YubiKey OTP authentication
10. Changing persistent data location
11. Changing the API request size limit
12. Changing the number of workers
13. SMTP configuration
14. Translating the email templates
15. Password hint display
16. Disabling or overriding the Vault interface hosting
17. Logging
18. Creating a systemd service
19. Syncing users from LDAP
20. Using an alternate base dir (subdir/subpath)
21. Other configuration

Database

1. Using the MariaDB (MySQL) Backend
2. Using the PostgreSQL Backend
3. Running without WAL enabled
4. Migrating from MariaDB (MySQL) to SQLite

Security

1. Hardening Guide
2. Fail2Ban Setup
3. Fail2Ban + ModSecurity + Traefik + Docker

Backup

1. General (not docker)

Other Information

1. Importing data from Keepass or KeepassX
2. Backing up your vault
3. Differences from the upstream API implementation
4. Supporting upstream development
5. Caddy 2.x with Cloudflare DNS