README
dsh-fleet-monitor · Fleet Monitor
A multi-host SSH monitoring panel for the DSH web GUI. It reuses the SSH credentials you already have, pulls every host from dsh-ssh and ~/.ssh/config into one console, and shows online state, CPU, memory, disk, network, and process counts — with per-host history charts and add/edit/delete from the panel itself.
Nothing to install on the monitored machines. The collector is a POSIX sh script that runs once over an existing SSH connection. The plugin only reads credentials already on your machine: no network egress, no telemetry.
Why another monitor
| Usual approach | This plugin | |
|---|---|---|
| Remote side | install an agent or exporter | nothing — sshd is the agent |
| Host inventory | maintain a second list | reuse dsh-ssh.json and ~/.ssh/config |
| Credentials | store them again | reuse yours; only panel-added hosts go into local SQLite |
| Scope | usually "this machine" | a fleet, N hosts polled in parallel |
| Data | one snapshot in memory | SQLite history, 24 hours by default |
Features
- Sections — six views behind hash routing (
#/overviewand friends) so a reload lands where it was: overview, servers, services, alerts, tasks, settings. The overview reduces the fleet to availability, memory and disk totals, what is alerting, and what is down; settings lays out the runtime facts unchanged. - Overview — stat cards (all / online / alerting / offline / panel-owned) that double as filters; search, group filter, sort by alias, CPU, memory, disk, latency, or state; table and card views; offline rows carry a red edge.
- Hosts — add, edit, and delete from the panel. Fields: alias, address, port, user, auth (key / password / agent), key path, passphrase, password, group, tags, note. Test connection before saving reports
12 ms · Ubuntu 24.04. Stored secrets are never sent back; leaving them blank on edit keeps the saved value. - Display metadata — display name, group, tags, note, expiry, price, bandwidth live in their own table. The alias itself is immutable: it is the join key for every sample already collected, so renaming would orphan that host's history.
- Detail — OS, kernel, arch, cores, CPU model, latency, uptime, swap, TCP/UDP, process count, plus three charts: CPU %, memory %, network KB/s over the last hour at 30-second resolution.
- Hardware — a slower sweep (five minutes by default) adds temperature, GPU, listening ports, per-mount disk usage, and per-NIC transfer totals.
- Service monitor — HTTP, TCP and ICMP probes on independent timers, from 10 seconds up. HTTP takes an expected status (
200,2xx,200,204,/^2\d\d$/) and a body keyword, and reads the certificate expiry off https targets six times a day. Each row shows a fixed 30-cell strip, padded on the left, so a probe added ten minutes ago does not look like a full day of uptime. Probes run from the DSH host, which is why they can watch a router with no SSH at all. - Alerts — rules over 19 metrics with a direction, a threshold, a duration, a cooldown, and a scope (all / only these / all but these). The duration becomes consecutive rounds (
180s ÷ 30s = 6), and offline needs at least two, because one missed sweep is a flaky network and two is a dead machine. A metric that readsnullfreezes the state instead of resolving it: one SSH timeout must not close an open incident and reopen it on the next round. The cooldown only gates re-entry into firing; a recovery always notifies. Events live in the local database, so a restart still knows what is on fire and does not open a duplicate. - Notifications — a generic HTTP template, not a list of providers: URL, method, body type, headers, body. Fifteen placeholders such as
#SERVER.NAME#,#RULE.NAME#,#VALUE#,#MESSAGE#; an unknown placeholder is left verbatim, because a typo should show up in the message rather than quietly become an empty string. Bark, Telegram, Lark and WeCom ship as presets with{token}-style placeholders. Send test answers 200 on success and 502 with the upstream message on failure. More than five notifications in one sweep collapse into a digest. - Scheduled tasks — five-field cron (
*,a-b,a/n, comma lists). The schedule is validated on save, including a refusal of dates that never arrive (0 0 30 2 *): a row that looks enabled and never fires is indistinguishable from a broken scheduler. Commands run over SSH on the covered hosts (all / only these / all but these), four at a time, with each host's own exit code and error kept; each host contributes up to 1 KB of output tail, the field is capped at 8 KB, and hosts that do not fit are named in the trailer instead of being dropped. Running a task while another is in flight answers 409 so the panel can say "busy" rather than "done". Each task keeps its last 500 runs, deleting the task deletes them, and a run that is more than an hour late is skipped rather than replayed.
更多「命令列與終端機」外掛
deepseek-harness-docker
作者 runzhliu
社群 Docker 與 Kubernetes 打包,含加固映象、Compose、Helm、Web UI 與無頭 CLI。
deepseek-harness-android
作者 dphmoblie
dsh安卓版:整合 DeepSeek Harness、Ubuntu 執行環境、外掛與檔案管理,以及使用者授權的 Shizuku 和無障礙自動化。
dsh-subagent-codex
作者 mjylfz
讓 DeepSeek Harness 以 Codex CLI 作為子代理的外掛,在對話中複用 Codex 的編碼與推理能力。
mnemon
作者 mnemon-dev
LLM 監督的持久記憶系統,基於圖結構召回、跨會話知識共享,單個二進位制檔案,相容 DeepSeek Harness 等執行時。
