Skip to content

Commit 49629ef

Browse files
[Docs][Core] Update system logs doc for dashboard subprocess module (#50984)
Signed-off-by: Chi-Sheng Liu <chishengliu@chishengliu.com>
1 parent 90c5a48 commit 49629ef

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

doc/source/ray-observability/user-guides/configure-logging.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,7 @@ System logs may include information about your applications. For example, ``runt
4747
### System/component logs
4848
- ``dashboard.[log|err]``: A log file of a Ray Dashboard. ``.log`` files contain logs generated from the dashboard's logger. ``.err`` files contain stdout and stderr printed from the dashboard. They're usually empty except when the dashboard crashes unexpectedly.
4949
- ``dashboard_agent.log``: Every Ray node has one dashboard agent. This is a log file of the agent.
50+
- ``dashboard_[module_name].[log|err]``: The log files for the Ray Dashboard child processes, one per each module. ``.log`` files contain logs generated from the module's logger. ``.err`` files contain stdout and stderr printed from the module. They're usually empty except when the module crashes unexpectedly.
5051
- ``gcs_server.[out|err]``: The GCS server is a stateless server that manages Ray cluster metadata. It exists only in the head node.
5152
- ``io-worker-[worker_id]-[pid].[out|err]``: Ray creates IO workers to spill/restore objects to external storage by default from Ray 1.3+. This is a log file of IO workers.
5253
- ``log_monitor.[log|err]``: The log monitor is in charge of streaming logs to the driver. ``.log`` files contain logs generated from the log monitor's logger. ``.err`` files contain the stdout and stderr printed from the log monitor. They're usually empty except when the log monitor crashes unexpectedly.

0 commit comments

Comments
 (0)