Monitoring

The MONITOR tab shows live system metrics for a connected server — CPU, RAM, disk, network, and running processes — refreshed every 2 seconds.

Opening Monitor

Click the MONITOR tab on any connected server. Metrics begin streaming immediately.

Gauges

Four arc gauges at the top of the panel:

Gauge	What it shows
CPU	Overall CPU utilisation (%)
RAM	Used / total RAM (%)
DISK	Root filesystem (/) used (%)
NET	Network I/O — inbound + outbound (KB/s)

Color thresholds:

• Green (OD): 0–70%
• Amber: 70–90%
• Red: 90–100%

All Disks

Below the gauges, each mounted filesystem is listed with a horizontal bar showing used/free space. Mount point, filesystem type, and raw values (GB used / GB total) are shown alongside each bar.

:::note Excluded mounts Loop devices (/dev/loop*) and snap mounts (/snap/*) are excluded — they always show 100% by design and aren't useful to monitor. :::

Process Table

The process table lists all running processes, sorted by CPU by default.

Columns: PID, Name, CPU %, Memory %, User, Status

Sorting: click any column header to sort ascending/descending.

Search: type in the filter box above the table to filter by process name.

Kill a process: right-click a row → Kill (sends SIGTERM) or Force Kill (sends SIGKILL). Both require confirmation.

Network Stats

Below the process table, per-interface network stats show:

• Interface name (e.g. eth0, ens3)
• Bytes received / sent since boot
• Current inbound / outbound rate (KB/s)

Cache & Cleanup

The CLEAR CACHE button runs sync; echo 3 > /proc/sys/vm/drop_caches on the server to flush page cache. Requires root or sudo access for the connected user.

caution

Clearing cache causes a brief spike in disk I/O as the OS repopulates it. Safe for production servers but expect a short performance dip.

The CLEANUP button runs a space-recovery script: removes old logs, apt/yum cache, and temp files. Review the output before approving each step — KoreShell prompts for confirmation.

Refresh Rate

Default: 2 seconds. Change in Settings → Monitoring → Refresh interval.

Lower values (1s) increase SSH channel traffic. Higher values (5–10s) are better for high-latency connections.

Alerts (coming soon)

Threshold-based alerts — notify when CPU > 90% or disk > 85% — are on the roadmap for a future release.