System Logs
The System Logs page provides a centralized view of application events stored in the database.
Log Levels
Section titled “Log Levels”| Level | Description |
|---|---|
| DEBUG | Detailed diagnostic information (only written when LOG_DEBUG=true) |
| INFO | General operational events (sync started, backup created, etc.) |
| WARN | Potential issues that don’t prevent operation |
| ERROR | Failures that require attention |
Log Categories
Section titled “Log Categories”| Category | Description |
|---|---|
| BACKEND | Core application logic events |
| API | API route handling and request processing |
| DB | Database operations and queries |
Viewing Logs
Section titled “Viewing Logs”The logs page displays:
- Timestamp — when the event occurred
- Level — severity (DEBUG, INFO, WARN, ERROR)
- Category — source category (BACKEND, API, DB)
- Source — specific component or function
- Message — description of the event
- Meta — additional contextual data (JSON)
Filtering
Section titled “Filtering”Filter logs by:
- Level — show only specific severity levels (INFO, WARN and ERROR are selected by default; tick DEBUG to see debug entries)
- Category — filter by source category
- Source — filter by specific component
- Search — case-insensitive text search across log messages
Auto-refresh
Section titled “Auto-refresh”Turn on Auto-refresh to re-read the current page every 5 seconds. The entry count and page total are updated every 30 seconds rather than on every refresh, since counting a large log table is the slow part; a newer page that appears in between still becomes reachable straight away.
Retention & Archival
Section titled “Retention & Archival”Configure log retention in Settings → General → Data Retention → Keep logs for:
- Range: 1 to 365 days (default: 7)
- Once an hour, logs from before today (days are counted in UTC) are archived to compressed
.tar.gzfiles, one per day, and removed from the database - Archive files older than the retention period are automatically pruned
Archives
Section titled “Archives”Archived logs are stored in /config/logs (configurable via the LOG_ARCHIVE_DIR environment variable). Each archive (logs-YYYY-MM-DD.tar.gz) contains a single day’s logs as one JSON file.
The System Logs page shows only the logs still in the database. To read an archive, open it from that directory on the host (it is under the /config volume by default).
Output
Section titled “Output”Logs are written to two destinations simultaneously:
- Database — the
LogEntrytable, accessible via the System Logs UI - Console — visible via
docker logsor your container runtime
This means you can view recent logs in the web UI and full container output via Docker.