Console Logs

Console Logs streams real-time system debug messages from a Director or Cluster instance. Use it to observe internal component activity, diagnose connectivity issues, and verify operational status without accessing server-side log files.

Console Logs is available on Director and Cluster detail pages only.

Accessing Console Logs

Navigate to Fleet Management > Directors and select a Director to open its detail view, then open the Console Logs tab. For Clusters, select a Cluster from the Clusters tab of the same page to open the Cluster detail view, which offers the same Console Logs tab.

Using Console Logs

The Console Logs panel provides a streaming text display with transport controls:

1. Configure capture parameters using the Filter button before starting
2. Optionally enter text in the query input field to restrict output to messages containing it — the field is disabled while a capture is running, so set it before starting
3. Click Capture to begin streaming — the button changes to Stop
4. Messages appear in the output area in monospace format with automatic scrolling
5. Click Stop to end capture, or wait for the capture time to elapse
6. Click the Copy button to copy all captured output to the clipboard — available only once capture has stopped and at least one message was received
7. Click Clean to clear the output and reset to idle state

Capture stops automatically when either the capture time or the capture count limit is reached, whichever occurs first.

Filter Options

Click the Filter button to open the filter popover. Configure these parameters before starting a capture:

Option	Type	Range	Default	Description
Severity Level	Multiselect	Error, Warning, Info, Debug	All selected	Log severity levels to include
Capture time in seconds	Number	5–60	10	Maximum duration of the capture session
Capture up to N events	Number	100–5,000	1,000	Maximum number of messages to capture

Values outside the valid range display an inline validation error under the field. Click Apply to save filter settings, or Cancel to discard changes. Filter settings persist for the duration of the browser session.

Severity Levels

Level	Description
Error	Failures requiring attention — connection errors, authentication failures, service exceptions
Warning	Conditions that may indicate problems — resource thresholds, deprecated configurations, retry attempts
Info	Normal operational messages — service startup, configuration loaded, connections established
Debug	Detailed diagnostic output — request/response traces, internal state changes, processing steps

Prerequisites

Console Logs requires the Director or Cluster to be both enabled and connected. When either condition is not met, the panel displays an alert explaining the issue:

• Director/Cluster is disabled — Enable the component from the Directors management page
• Director/Cluster is not connected — Verify the Director service is running and network connectivity is available

---