Files
platform/SYSTEM_MONITOR_API.md
T
pastilhas 027b10bd6e step 4/4: the docs say permissions too, and capability means one thing again
44 files of prose — CLAUDE.md, AGENTS.md, TODO.md, 20 docs, both plugin design
documents, and the comment surface the earlier steps could not reach.

Applied against an explicit keep-list, not swept, because the word turned out to
have SIX meanings in this repository rather than the three the offscale doc
recorded:

  permissions          renamed (steps 1–2)
  $OFFICER_ROOT/capabilities/  KEPT — the item store, and now the only thing
                               the word means that is ours
  sidecar routing keys renamed to `handles` (step 3)
  Lightning wallet     KEPT — a domain term, and on the wire to the mobile apps
  terminfo queries     KEPT — XTGETTCAP, in the pty sidecar
  InvoiceShelf         KEPT — per-resource { write, bulkDelete } flags

The sweep still falsified two things, both caught by checking rather than by
review, and both in prose that discusses more than one meaning at once:

CLAUDE.md began claiming the item store lives at `$OFFICER_ROOT/permissions`.
It does not; that directory is on disk and full of skills and tools.

And the offscale doc's own note about the collision became
"Named `permissions`, NOT `permissions`" — a sentence that had eaten the thing
it existed to warn about.

Both restored, and the note rewritten to say what is now true: capability means
one thing of ours, and three that belong to somebody else's vocabulary.

Verified live after restart: self and admin permission endpoints 200, gated
route 200, agent-status 200, 9 grants intact with 6 permissions offered.
tsgo clean, 797 tests, 787 pass, same 7.

The rename is done. Four steps, no data lost, no client break that survived
the step it was introduced in.
2026-08-15 16:31:11 +00:00

5.4 KiB
Raw Blame History

System Monitor API (/api/system-monitor/*)

Everything the /system-monitor web screen renders, for building the same in the app.

Auth & access

  • Send the JWT as Authorization: Bearer <token>, or as ?token=<token> in the query string (required for the SSE endpoints — EventSource can't set headers).
  • Owner-only. These routes belong to the server-admin permission, which is kind: 'admin' and therefore never grantable — a non-owner account gets 403 here whatever its role. The full officer-mobile client (which authenticates as the owner) has access; the music app does not.
  • Note for anyone who read this before 2026-08-07: the old rule was that non-owner accounts were confined to a hardcoded /api/auth + /api/music. That list is gone, replaced by per-role permission grants. The outcome for these routes is unchanged — still owner-only — but the reason is now the permission's kind, not a two-element array.
  • All responses are application/json except the two /logs endpoints, which are text/event-stream.

GET /api/system-monitor/stats

One full snapshot. Poll it on a steady interval (the web client uses 2 s) — a few fields are rates computed from the delta since your previous call (see notes), so a steady cadence matters.

{
  "hostname": "alpha",
  "platform": "Linux 6.8.0-136-generic",
  "uptimeSec": 614031,
  "loadavg": [0.59, 0.60, 0.81],          // 1 / 5 / 15 min
  "cpu": {
    "model": "AMD Ryzen 9 7940HS w/ Radeon 780M Graphics",
    "cores": 16,
    "usagePct": 2.6,                       // overall, 0100
    "perCore": [3.1, 0.0, 12.4, ...]       // length === cores
  },
  "mem": {                                 // null if unreadable
    "totalBytes": 65100000000, "usedBytes": 26800000000, "freeBytes": 38300000000,
    "usedPct": 41.2, "swapTotalBytes": 0, "swapUsedBytes": 0
  },
  "disks": [                               // real mounts (tmpfs/overlay excluded)
    { "mount": "/", "fsType": "ext4", "totalBytes": 0, "usedBytes": 0, "usedPct": 32 }
  ],
  "processes": [                           // top 20 by CPU
    { "pid": 1234, "user": "pastilhas", "cpuPct": 21.8, "memPct": 1.2, "command": "radicle-node" }
  ],
  "temp": {                                // null if no hwmon
    "cpuC": 56.0,                          // chosen CPU sensor, °C (null if none matched)
    "cpuLabel": "k10temp · Tctl",
    "sensors": [ { "name": "amdgpu", "label": "edge", "celsius": 55.0 }, ... ]  // every hwmon temp
  },
  "gpu": {                                 // null if no /sys/class/drm gpu_busy_percent
    "busyPct": 0, "vramUsedBytes": 2092957696, "vramTotalBytes": 2147483648
  },
  "net": {                                 // null if /proc/net/dev unreadable
    "rxBytesPerSec": 0, "txBytesPerSec": 0,           // aggregate (excludes lo)
    "interfaces": [ { "name": "eth0", "rxBytesPerSec": 0, "txBytesPerSec": 0 } ]  // active only, busiest first
  },
  "power": {                               // null if unreadable
    "cpuWatts": null,                      // RAPL is root-only by default → usually null
    "gpuWatts": 38.1                       // amdgpu hwmon
  },
  "timestamp": 1785150000000
}

Notes

  • net.*BytesPerSec and power.cpuWatts are deltas since the previous /stats call. The first call returns 0/null for these; steady-interval polling gives stable numbers.
  • cpuWatts is usually null — RAPL energy_uj is root-only unless a udev rule opens it. gpuWatts works.
  • Any section can be null on hardware that doesn't expose it — render defensively.

GET /api/system-monitor/pm2

{
  "processes": [
    {
      "id": 0, // pm2 id (pm_id) — use this for the logs endpoint
      "name": "officer",
      "status": "online", // online | stopped | errored | …
      "pid": 3339851, // OS pid, or null
      "cpuPct": 0,
      "memBytes": 10354688,
      "restarts": 44,
      "uptimeMs": 420000,
    }, // 0 unless status === "online"
  ],
  "error": "…", // present only if pm2 couldn't be read
}

GET /api/system-monitor/docker

{
  "containers": [
    {
      "id": "abc123def456", // short id (12 chars) — use for the logs endpoint
      "name": "jellyfin",
      "image": "jellyfin/jellyfin",
      "state": "running", // running | exited | …
      "status": "Up 3 hours",
      "ports": "0.0.0.0:9301->8096/tcp",
    },
  ],
  "error": "…",
}

Live logs (SSE)

Both stream one data: <log line> frame per line, plus : hb heartbeat comments every 15 s. The server kills the underlying tail when the connection closes. Open with EventSource using ?token=.

GET /api/system-monitor/pm2/logs?id=<pm_id>&lines=<n>

  • idnumeric pm2 id from /pm2 (required).
  • lines — initial backlog, default 100, max 1000.
  • Source: pm2 logs <id> --raw (combined stdout+stderr, follows live). The first frames include a short pm2 [TAILING] … header.

GET /api/system-monitor/docker/logs?id=<container>&lines=<n>

  • id — container id or name from /docker (charset-validated).
  • lines — initial backlog (--tail), default 100, max 1000.
  • Source: docker logs -f --tail <n> <id> (combined stdout+stderr).
const es = new EventSource(`/api/system-monitor/pm2/logs?id=0&lines=150&token=${token}`);
es.onmessage = (e) => appendLine(e.data);
// close es to stop the tail