Mirrors/Sonarr
1
0
Fork 0
mirror of https://github.com/Sonarr/Sonarr.git synced 2024-11-22 02:32:51 +01:00
Code Issues Releases Wiki Activity

Updated Logging and Log Files (markdown)

Donald Webster 2019-11-12 13:10:26 -08:00
parent 6b10400226
commit 6231ccd493
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Logging-and-Log-Files.md

@ -3,6 +3,9 @@ The log files are located in Sonarr's [AppData directory](https://github.com/Son
**Note**: the Logs Table in the UI is _not_ the same as the log files.
### Sharing Logs
The log files can be long and hard to read as part of a forum or reddit post. And they're spammy in IRC or Discord, so *please* use a [pastebin](https://paste.ubuntu.com). The whole file typically isn't needed, just a good amount of context around the issue/error. Don't forget to wait for spammy tasks to finish, like the RSS sync or library refresh.
### Trace/Debug Logs
You can change the log level at Settings -> General -> Logging. Sonarr does not need to restarted for the change to take effect. This change only effects the log files, not the logging database. The latest debug/trace log files are named `sonarr.debug.txt` and `sonarr.trace.txt` respectively.
@ -27,6 +30,3 @@ Sonarr uses rolling log files limited to 1MB each. The current log file is alway
When Debug log level is enabled, additional `sonarr.debug.txt` rolling log files will be present, up to 51 files. This log files contains fatal,error,warn,info *and* debug entries. It usually covers a 40h period.
When Trace log level is enabled, additional `sonarr.trace.txt` rolling log files will be present, up to 51 files. This log files contains fatal,error,warn,info,debug *and* trace entries. Due to trace verbosity it only covers a couple of hours.
### Sharing Logs
The log files can be long and hard to read as part of a forum or reddit post. And they're spammy in IRC or Discord, so *please* use a [pastebin](https://paste.ubuntu.com). The whole file typically isn't needed, just a good amount of context around the issue/error. Don't forget to wait for spammy tasks to finish, like the RSS sync or library refresh.