RPJosh
/
authelia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: include stdout information about complete logs (#5346) 

Signed-off-by: James Elliott <james-d-elliott@users.noreply.github.com>
pull/5347/head
James Elliott 2023-05-01 13:44:39 +10:00 committed by GitHub
parent eaddb57c27
commit 9006ff6979
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/content/en/reference/guides/troubleshooting.md
View File

@ -30,6 +30,19 @@ log files. In addition the [log level](../../configuration/miscellaneous/logging
Complete logs means at minimum from the [log severity line](#log-severity-line) until the actual issue occurs. Though
more than this may be included at the users discretion.
### Output
Logging can be [configured](../../configuration/miscellaneous/logging.md) to output to both a file and stdout / console
/ docker logs.
- If you configure the [file_path] option with the [keep_stdout] configuration option enabled then you will only be
required to supply the stdout / console / docker logs and should ignore the file logs.
- If you configure the [file_path] option without the [keep_stdout] configuration option enabled then you will be
required to join the stdout / console / docker logs with the file logs.
[keep_stdout]: ../../configuration/miscellaneous/logging.md#keepstdout
[file_path]: ../../configuration/miscellaneous/logging.md#filepath
### Large Amount of Logs
In instances where the logs are substantial we will accept truncated logs. There are however some very intentional rules