mitchell/hamlab
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 14 Wiki Activity

A Top tab: the whole machine on one screen, in btop's style

Browse Source 
Boxes with their name in the border, dot curves that climb green to red, per-core meters and
temperatures, memory and filesystems, per-interface traffic and the process table. Drawn from
the sensor stream and /api/procs, so it works on every machine the console can see.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Mitchell-Johnson
2026-09-20 23:52:29 -07:00
co-authored by Claude Opus 5
parent b8eb4f5d40
commit 0587f50142
4 changed files with 539 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SENSORS.md
+9
View File
@@ -199,6 +199,15 @@ GET /api/fleet/sensors/query?machines=grid,wyse&cpu=cpu.usage&failed=services.f
→ {"core": {"cpu": 4.8, "up": 50211}, "grid": {"cpu": 0.4, "up": 437177}, "mac": {"error": "timeout"}}
```
## The Top tab
Ham Lab → **Top** is a whole machine on one screen in the style of btop: black ground, boxes
with their name set into the border, curves drawn as dots that climb green → yellow → red.
It reads nothing of its own — the sensor stream for everything measured, `/api/procs` for the
table — so it works on any machine the console can reach, whether or not btop is installed
there, and it follows the same refresh rate and history window as the rest of the console.
(The look is btop's, `web/src/Top.tsx` is ours; btop itself is Apache-2.0.)
## How far back a history reaches
Every machine keeps **300 points per curve**, whatever the window — so the window sets how