SHTops
The SuperHiTech operations and monitoring host — what runs on it, how Leif reaches it, and the rules that keep tool routing honest.
SHTops is SuperHiTech’s primary operations host — the monitoring, alerting, and
automation surface that sits behind the shtops_* tool family. It’s a separate
machine from Leif (10.10.0.25) and nvrbackup (10.10.0.14), with its own tool
namespace precisely because it’s a distinct ops surface.
Host facts
| Field | Value |
|---|---|
| Hostname | shtops |
| Internal IP | 10.10.0.24 |
| Platform | Proxmox guest VM (kernel 6.8.x-pve) |
| WireGuard interfaces | 172.20.11.x (customer-site monitoring reach) |
| Workspace | /home/superht/shtops/ |
| Python venv | /home/superht/shtops/venv/ |
| Living docs | /home/superht/shtops/docs/ |
| Handoffs | /home/superht/shtops/handoffs/ |
| Tool routing | shtops_execute_command for shell, shtops_* for scoped operations |
There are no dedicated SHTops file read/write tools — shtops_execute_command
is the read/write workhorse (use cat, sed, tee, etc.).
What runs on it
| Service | Listens | What it is |
|---|---|---|
shtops-dashboard (systemd) | 0.0.0.0:5000 | The ops dashboard / API — Python dashboard.app from the venv, WorkingDirectory=/home/superht/shtops |
| Slack webhook | 0.0.0.0:3000 | /home/superht/slack_webhook.py — inbound Slack event/webhook handler |
| Local tooling | 127.0.0.1:18732 | Node process bound to localhost only |
The dashboard exposes an authenticated API used by AI assistants and
automation. Tokens are shtops_live_* strings, supplied via the
SHTOPS_API_TOKEN environment variable (or config/config.yaml). See
docs/AI_ASSISTANT_QUICKSTART.md and docs/API_INTEGRATION.md on the host.
SHTops tools
| Tool | Purpose |
|---|---|
shtops_execute_command | Run a shell command on the host (also the file read/write path) |
shtops_get_system_info | Host identity check — returns node: shtops, kernel, uptime |
shtops_get_status | Online status + system summary (compact / full) |
shtops_check_service | Status of a named systemd service |
shtops_restart_service | Restart a named systemd service |
shtops_list_processes | High-memory process listing |
shtops_list_tasks | Supported automation tasks (see below) |
shtops_bootstrap | Alias for bootstrap_context(scope='shtops') — pulls living docs |
Supported automation tasks
shtops_list_tasks reports the sanctioned, structured operations:
| ID | Name | System |
|---|---|---|
remote_shell | Execute Shell Command | OS |
restart_service | Restart Service | OS |
reboot | Reboot System | OS |
What it’s responsible for
SHTops is the hub for SuperHiTech’s internal monitoring and ops integrations.
The living docs under /home/superht/shtops/docs/ cover, among others:
- Monitoring & alerting — LibreNMS client onboarding runbooks, alert triage
plans, and the internal-monitoring design (the “who watches the watchers”
work). Alerts route to ntfy topics:
shtops-alerts/shtops-hq-alerts(internal) andcustomer-alerts-critical/customer-alerts-info(customer). - UniFi — SHTops holds the local JSON caches that the
unifi_*tools read.unifi_*is not a live controller call; it reads caches on this host. - Backups — MSP backup alert remediation and the Storj v2 migration.
- Endpoint security — Bitdefender push-event ingestion.
- Business integrations — QuickBooks (OAuth), Slack, Gmail / Google Workspace, and ConnectWise Automate instruction wiring.
Related pages
- Hosts — full host inventory and tool routing summary
- Service Map — services and the Leif tools that manage them
- Network Topology — VPNs and customer-site reach
- Tools — the
shtops_*,unifi_*, andpve_*namespaces
Last verified against live systems: 2026-06-01 — see doc freshness.