Skip to main content

SysDash - Real-Time System Monitoring Dashboard

Real-time terminal-based system monitoring with beautiful graphs and customizable views.

Installation

Option 1: Install from PyPI (using pip)

pip install sysdash-cli
or
pip install git+https://github.com/thulasiramk-2310/cli_metrics.git

Option 2: Run with Docker (Linux only)

# Pull from Docker Hub
docker pull ram231006/sysdash:latest

# Run on Linux with host system access (requires sudo for some metrics)
sudo docker run -it --rm --pid=host --net=host ram231006/sysdash:latest

# Run the mini dashboard
sudo docker run -it --rm --pid=host --net=host ram231006/sysdash:latest sysdash-mini

# ⚠️ Note: Docker on Windows/macOS shows container metrics, not your actual system.
# For accurate Windows/macOS monitoring, use pip install instead (Option 1 or 3).
# Docker works perfectly on native Linux systems with sudo.

Option 3: Clone and install locally

git clone https://github.com/thulasiramk-2310/cli_metrics.git
cd cli_metrics
pip install -e .

Quick Start

sysdash

Beautiful graphs, colors, and real-time visualizations.

Simple Text Dashboard

sysdash-mini

Lightweight ASCII version - perfect for SSH sessions and basic terminals.

Features

📊 System Metrics

  • ✅ CPU Metrics: Total usage, per-core usage, frequency, load average
  • ✅ Memory Metrics: Total, used, available, free, swap
  • ✅ Disk Metrics: Partition usage, I/O rates (read/write)
  • ✅ Network Metrics: Upload/download rates, total transfer, packets
  • ✅ Process Metrics: Top processes by CPU and memory usage
  • ✅ System Info: Hostname, uptime, real-time updates

⌨️ Interactive (sysdash only)

  • Toggle panels live: 1 CPU, 2 memory, 3 disk, 4 network, 5 processes
  • Kill processes: select with ↑/↓, press k, then confirm
  • Built-in help: press h for the full key reference
  • Quit: q

📈 Visualizations (sysdash only)

  • Real-time Line Graphs: Smooth trend lines with color-coded indicators
    • 🔴 Red: CPU/Memory increasing (high load warning)
    • 🟢 Green: CPU/Memory decreasing (optimizing)
  • Progress Bars: Visual usage indicators for all metrics
  • Live Updates: Configurable refresh intervals (0.1s - 10s)
  • 60-Second History: Rolling graph showing usage trends
  • Resizes with your terminal: panels and the per-core grid re-flow as the window changes, from 60 columns up to full screen
  • Every core shown: the grid wraps into as many columns as fit

🎨 Customizable Views

  • Full Dashboard: All metrics at once
  • CPU Only: --cpu-only
  • Memory Only: --memory-only
  • Disk Only: --disk-only
  • Network Only: --network-only
  • Processes Only: --processes-only
  • Custom Combinations: Use --no-* flags to hide specific metrics

Usage

Graphical Dashboard (sysdash)

# Full dashboard with graphs (all metrics)
sysdash

# Faster updates (every 0.5 seconds)
sysdash --interval 0.5

# Custom hostname
sysdash --hostname production-server-01

Simple Dashboard (sysdash-mini)

# Basic text dashboard
sysdash-mini

# Custom interval
sysdash-mini --interval 2

# Custom hostname
sysdash-mini --hostname my-server

Customized Views (sysdash)

# Show only CPU metrics with graph
sysdash --cpu-only

# Show only disk metrics
sysdash --disk-only

# Show CPU and memory only
sysdash --no-disk --no-network --no-processes

# Show everything except processes
sysdash --no-processes

# CPU only with fast updates
sysdash --cpu-only --interval 0.3

Keyboard Controls (sysdash)

The dashboard is interactive — panel choices can be changed while it runs, so the --*-only and --no-* flags are only needed to set the starting view.

Key Action
h ? Show or hide the help panel
1 Toggle CPU metrics
2 Toggle memory metrics
3 Toggle disk metrics
4 Toggle network metrics
5 Toggle the process list
↑ ↓ Move the selection in the process list
k Kill the selected process (asks for confirmation)
y Confirm: terminate (SIGTERM), letting the process clean up
K Confirm: force kill (SIGKILL), no cleanup
n Esc Cancel a pending kill
q Quit

Each key press is reported in the footer, so a panel toggling off is never silent.

Killing processes

k never acts immediately — it stages the kill and waits for confirmation. System processes (PID 0/1/4, System, systemd, init, launchd) and sysdash's own process are refused outright.

Killing a process owned by another user needs elevation: run with sudo on Linux or as Administrator on Windows. Without it the footer reports Permission denied rather than failing silently.

Command-Line Arguments

sysdash (Graphical Dashboard)

Argument Type Default Description
--interval float 1.0 Update interval in seconds (min: 0.1)
--hostname str system hostname Custom hostname identifier
--cpu-only flag false Show only CPU metrics
--memory-only flag false Show only memory metrics
--disk-only flag false Show only disk metrics
--network-only flag false Show only network metrics
--processes-only flag false Show only process list
--no-cpu flag false Hide CPU metrics
--no-memory flag false Hide memory metrics
--no-disk flag false Hide disk metrics
--no-network flag false Hide network metrics
--no-processes flag false Hide process list

sysdash-mini (Simple Dashboard)

Argument Type Default Description
--interval float 1.0 Update interval in seconds
--hostname str system hostname Custom hostname identifier

Dashboard Layout

Graphical Dashboard (sysdash)

╔════════════════════════════════════════════════════╗
║ SysDash CLI | Host: YourPC | Uptime: 00:05:23     ║
╚════════════════════════════════════════════════════╝
╭──────── CPU & Memory ────────╮╭───── Disk ──────╮
│ CPU:    45.2% ████████░░░░   ││ C:\ 48% Used    │
│ Memory: 68.5% █████████████░ ││ D:\ 30% Used    │
│ Per-Core Usage               ││ I/O Rates       │
╰──────────────────────────────╯╰─────────────────╯
╭──────── Usage Trends ────────╮╭──── Network ────╮
│ 📈 CPU Usage Trend           ││ Up: 125 KB/s    │
│ Max: 85.7%                   ││ Dn: 89 KB/s     │
│ [Line graph]                 ││ Total Transfer  │
│ Min: 12.3%                   ││ Packets         │
╰──────────────────────────────╯╰─────────────────╯

Simple Dashboard (sysdash-mini)

=== SysDash Mini ===
Host: YourPC | Uptime: 00:05:23

CPU: 45.2% ████████████░░░░░░░░
Memory: 68.5% █████████████░░░░░░░
Disk C:\ 48% | Network: ↑125 KB/s ↓89 KB/s

Requirements

  • Python 3.7+
  • psutil 5.9.0+
  • rich 13.0.0+ (for sysdash only, not required for sysdash-mini)

Troubleshooting

Permission denied errors on Linux?

  • Run with sudo: sudo sysdash or sudo sysdash-mini
  • For Docker: sudo docker run -it --rm --pid=host --net=host ram231006/sysdash:latest
  • Some system metrics require elevated permissions

Graph not displaying? (sysdash)

  • Graphs need two data points, so give it a couple of update intervals
  • Press 1 or 2 to check CPU/memory panels have not been toggled off

Updates too slow/fast?

  • Adjust with --interval (recommended: 0.5 - 2.0 seconds)

Terminal too small?

  • Panels re-flow automatically as you resize, down to about 60 columns
  • Below that, hide panels with 1-5 or use sysdash-mini

A panel disappeared?

  • You most likely pressed its number key. The footer says which, and the same key brings it back. Press h for the full list.

Colors not showing?

  • Check if your terminal supports ANSI colors
  • Use sysdash-mini for basic ASCII output

SSH/Remote connection issues?

  • Use sysdash-mini for better compatibility
  • Some terminal emulators may not support Rich features

Development

git clone https://github.com/thulasiramk-2310/cli_metrics.git
cd cli_metrics
pip install -e ".[dev]"
pytest

The suite renders the dashboard against fixed metrics and compares the output against snapshots in tests/snapshots/, so layout regressions fail loudly. If a render change is intentional, refresh them:

SYSDASH_UPDATE_SNAPSHOTS=1 pytest

Tests marked real_psutil use live readings instead of stubs; everything else is deterministic and runs in about two seconds. GitHub Actions runs the suite on Linux and Windows across Python 3.9, 3.11 and 3.13.

Reporting wrong readings

If a metric looks wrong on your machine, scripts/diagnose.py prints what psutil reports next to free -h, /proc/meminfo and df, flags any inconsistency, and detects immutable or containerised systems:

python3 scripts/diagnose.py

Include its output in the issue.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License

Metadata

Release files for sysdash-cli 1.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sysdash-cli 1.1.0
File Size Uploaded Provenance Actions
sysdash_cli-1.1.0.tar.gz 31.9 kB Without provenance Details for sysdash_cli-1.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for sysdash-cli 1.1.0
File Interpreter ABI Platform Actions
sysdash_cli-1.1.0-py3-none-any.whl Python 3 none any Details for sysdash_cli-1.1.0-py3-none-any.whl

Total release size: 55.7 kB

Release files / sysdash_cli-1.1.0.tar.gz

Download URL sysdash_cli-1.1.0.tar.gz
Size 31.9 kB
Tags Source
SHA-256 checksum
How to use checksums
03e877177b117e6a40e2c62f748f39bb320af3f8a5997a919d4d5054dad230f7
BLAKE2b-256 checksum
How to use checksums
7ce317fdf5a78d0facef5964698e9f8fe50e2e021614f57e18102b1d21b26030
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.2

Release files / sysdash_cli-1.1.0-py3-none-any.whl

Download URL sysdash_cli-1.1.0-py3-none-any.whl
Size 23.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d9b38fd45404d06c5ce6d9ce13b23e5e297ae6c0cd17c68a41131875b5618893
BLAKE2b-256 checksum
How to use checksums
69a43cbf241b87fca97cc641f9942a05669b9776ac3dbc03aa551bef32806bf8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.2

Security for sysdash-cli 1.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page