mirror of
https://github.com/zadam/trilium.git
synced 2025-11-14 09:15:50 +01:00
34 lines
1.7 KiB
Markdown
Vendored
34 lines
1.7 KiB
Markdown
Vendored
# Backend (server) logs
|
||
## Accessing via the backend log
|
||
|
||
In the <a class="reference-link" href="../../Basic%20Concepts%20and%20Features/UI%20Elements/Global%20menu.md">Global menu</a>, go to Advanced → Show backend log
|
||
|
||
## Location on the disk
|
||
|
||
Backend logs are stored on the file system. To find them, open the <a class="reference-link" href="../../Installation%20%26%20Setup/Data%20directory.md">Data directory</a>, go to the `log` subdirectory and find the latest log file, e.g. `trilium-2022-12-14.log`.
|
||
|
||
## Reporting backend bugs
|
||
|
||
You can attach the whole file to the bug report (preferable) or open it and copy-paste only the last lines / lines you believe are relevant.
|
||
|
||
## Customizing the retention of logs
|
||
|
||
The backend logs are fully managed by the Trilium server. By default the last 90 days worth of logs are kept; the logs older than that are deleted in order to reduce the space consumption.
|
||
|
||
It's possible to change the retention period by modifying the <a class="reference-link" href="../../Advanced%20Usage/Configuration%20(config.ini%20or%20e.md">Configuration (config.ini or environment variables)</a> via the `.ini` file:
|
||
|
||
```
|
||
[Logging]
|
||
retentionDays=7
|
||
```
|
||
|
||
Or via the environment variable `TRILIUM_LOGGING_RETENTION_DAYS`.
|
||
|
||
Special cases:
|
||
|
||
* Positive values indicate the number of days worth of logs to keep
|
||
* A value of 0 results with the default value (90 days) to be used
|
||
* Negative values (e.g. `-1`) result with all logs to be kept, irrespective how ancient and numerous (and
|
||
|
||
> [!NOTE]
|
||
> If you set the retention days to a low number, you might notice that not all the log files are being deleted. This is because a minimum number of logs (7 at the time of writing) is maintained at all times. |