Maintenance & License•5 min read•Diagnostics

System Diagnostics & Interactive Web Terminal

Monitor controller host resources, Redis queues, and OCI container workloads, and connect to remote servers using the integrated SSH web terminal.

CIEL includes built-in system diagnostics and an interactive SSH web terminal directly in the web interface. Administrators can monitor controller capacity, background worker queues, and runner container environments without logging into the controller host over SSH.

Operators can also connect to managed servers directly from their browser, eliminating the need to distribute private key files or open direct SSH access from personal workstations.

System Diagnostics Health Telemetry, Redis Queue, and Runner Containers

1. System Diagnostics Workspace (/system)

The System Diagnostics interface is accessible under the Administration menu (/system). It groups controller metrics and background services into six functional tabs:

A. Overview & Health

Provides a status summary of the controller host and automation dependencies:

  • Host Resources: Real-time CPU utilization percentage, physical memory consumption (used and total), and disk space allocated to the CIEL data directory.
  • Ansible Core Runtime: Confirms whether Ansible is installed, displaying the core version (e.g. ansible [core 2.16.x]), executable location, and Python runtime.
  • Container Engine: Reports the availability of the Podman execution runtime and confirms whether the official base execution environment image (quay.io/ansible/creator-ee) is cached locally.

B. License & Quotas

Displays current subscription boundaries and live resource usage:

  • Quota meters for managed hosts, project workspaces, team members, provisioners, and inbound webhooks.
  • Available capacity indicators showing used versus remaining resource slots.
  • Active feature flags, such as role-based access control (RBAC), two-way SaaS callbacks, and execution log retention windows.

C. Host Capacity

Detailed breakdown of compute overhead on the controller server:

  • System load averages across 1-minute, 5-minute, and 15-minute intervals.
  • Memory distribution comparing active RAM usage against virtual swap memory.
  • Helps operators evaluate whether the host has sufficient capacity to increase parallel runner concurrency.

D. Redis & Queue

Monitors the message broker responsible for job queueing and live execution streaming:

  • Service State: Connection status (ok, disabled, or error) and Redis server version.
  • Connected Clients: Number of active worker and API connections communicating with Redis.
  • Memory Overhead: Total memory consumed by cached data and message streams.
  • Queue Depth: Number of pending execution jobs waiting in the queue.

E. Podman Workloads

Inspects containerized execution environments running on the controller:

  • Container Instances: Table of active and completed runner containers, including container IDs, names, base images, lifecycle state (running, exited), and forwarded ports.
  • Cached Images: Table of downloaded container images, detailing repository tags, image IDs, disk usage, and creation dates.

F. Active Processes

Live process inspection on the controller server:

  • Lists active operating system processes sorted by CPU and resident memory usage.
  • Search filter to quickly locate processes by PID, command name, or user.
  • Useful for identifying long-running runner worker subprocesses or unexpected resource spikes.

2. Interactive Web Terminal

The integrated Web Terminal allows operators to open secure shell sessions to target servers directly from the browser interface.

Key Capabilities

  • Full PTY Emulation: Operates as a complete terminal console supporting ANSI colors, window resizing, and full-screen terminal programs such as htop, vim, nano, top, and less.
  • Zero Local Client Configuration: Connects through the CIEL controller using the credentials, SSH keys, or passwords already configured for the host. Operators do not need local SSH clients or VPN software on their laptops.
  • Multi-Tab Sessions: Open multiple terminal tabs simultaneously to manage different target nodes in parallel without switching windows.
  • Host Key Verification: Verifies remote server fingerprints against recorded keys to protect connections against spoofing or unauthorized server replacements.
  • Encrypted Credential Isolation: Assigned SSH keys and passwords are used exclusively by the controller to establish the connection and are never transmitted to the browser.

3. Terminal Access Workflows

Operators can launch web terminal sessions from two primary locations in CIEL:

A. Host SSH Console Drawer (Global)

Available from any host view in your project:

  1. Navigate to Hosts under your active project workspace.
  2. Click the SSH Terminal button (>_) on any host card or list row.
  3. The Host SSH Console opens as a floating modal window.

Drawer controls include:

  • Tab Navigation: Click any tab to switch between active server sessions.
  • Connection Indicators: Live status dots indicate whether each session is connected (green), connecting (amber), or disconnected (red).
  • Fullscreen Mode: Expand the terminal window to fullscreen for comfortable file editing or diagnostic workflows.
  • Disconnect All: Terminate all active terminal connections at once using the disconnect button.

B. Studio Workbench Side Terminal (Playbook Authoring)

Available inside the Studio playbook workbench (/studio):

  1. In the top toolbar, select a target host from the execution dropdown.
  2. Click the SSH: <host_name> button.
  3. A docked terminal pane opens directly alongside the Monaco code editor.

This side-by-side view allows operators to inspect remote directories, test shell syntax, or verify service status while authoring playbook tasks. While the side terminal is open, execution actions are locked to prevent conflicts between manual commands and automated runs.


4. Connection Troubleshooting

IssueTypical CauseRecommended Action
Connection rejected / Permission deniedIncorrect credentials or rejected key.Verify the assigned SSH key in Key Vault or check username and password variables on the host.
Host key verification warningThe remote host key changed or the server was reinstalled.Confirm whether the server was intentionally rebuilt before accepting the new fingerprint.
Connection timed outTarget host port 22 is unreachable.Check server IP address, network routing, and security group firewall rules.
Execution locked in StudioSide terminal is currently active.Close the side terminal panel in Studio before starting a playbook run or dry run.