Resource Monitoring
The Resource Monitoring view in the Account app shows live telemetry for the machine you’re working on — running containers, CPU/memory usage, storage, and per-service status — plus a recent-activity feed of commits and incidents.
Local-first by design
Even though the Account app is served over HTTPS from Nanokit’s servers, the
monitoring view connects only to the bridge running on your own machine
(http://127.0.0.1:3006). Browsers treat http/ws to 127.0.0.1 as a secure
context, so the loopback connection works from the HTTPS page.
It never falls back to a remote/server bridge — that would show server data instead of yours. When no local bridge is reachable (for example, on a phone, or when the bridge isn’t running) the view shows a clear “No local bridge detected” state with a Retry button.
Start the bridge with nkapp up (which starts everything, the bridge
included) or nkapp hub (which starts just the bridge) on the machine you want
to monitor, then hit Retry.
What it shows
| Panel | Source |
|---|---|
| Active environments & running containers | Bridge discovery (re-scanned periodically). |
| CPU / memory / disk usage | Live system stats streamed over the bridge WebSocket. |
| Per-service status | Service reconciliation state for the selected environment. |
| Recent activity | Git commits (message, author, branch, tags) and incidents. |
Use the environment selector to switch which environment’s containers you’re watching; your selection is remembered.
For the architecture of the bridge itself (local vs. remote, telemetry, team scoping), see Architecture → Bridge & Telemetry.