-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #93 from nichwall/log_guide
Add: logs guide
- Loading branch information
Showing
2 changed files
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: Server logs | ||
slug: server_logs | ||
fullpath: /guides/server_logs | ||
--- | ||
|
||
--- | ||
|
||
# Introduction | ||
This page discusses how logging works on the server. | ||
Log settings are located in the server settings under "Logs" in the left pane. | ||
|
||
# Server Logs | ||
By default, server log levels are set to `Info`. | ||
The 3 log levels in order of increasing information are `Warn`, `Info`, and `Debug`. | ||
Logs can be viewed in the web browser, but all logs are stored in `/metadata/logs` as JSON files. | ||
Note that logs are stored based on the log level setting, so if you are logging as `Info` no `Debug` logs are stored. | ||
|
||
![Log Settings](/guides/server_logs/logs.png) | ||
|
||
# Crash logs | ||
Beginning with server version 2.8.0, crash logs are stored in `/metadata/logs/crash_logs.txt`. | ||
This file will include more information than the normal log files. | ||
If the server is crashing and you do not see anything in `crash_logs.txt`, you will need to check the logs of however you are running the server (Docker container logs, etc). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.