Audiobuzz
1c68c37824
The agent only reported chrony as synced|unsynced — nothing about how well the
clock tracks. Parse `chronyc tracking` for the source-relative metrics.
- proto: HealthSnapshot.chrony_offset_seconds (16, signed system-time offset,
fast=+), chrony_source (17, reference name/IP), chrony_stratum (18); regenerated.
- agent: replace chronyState() with chronyTracking()/parseChrony() — one exec,
parses Leap status + Reference ID + Stratum + System time offset (+ test).
- manager: Health.{ChronyOffset,ChronySource,ChronyStratum}; snapshotToHealth maps
them; influx writes chrony_offset_seconds/_stratum/_source and whitelists the
offset + stratum as graphable fields.
- UI: chronySummary() + offsetMs() — the chrony row now shows
"synced · 192.168.50.10 · s3 · +0.01ms" instead of just "synced".
fleet-manager UI — the fleet command deck
The admin SPA for fleet-manager. Svelte 5 + Tailwind 4 + Vite, themed
LYSANDRA / restricted-violet (a high-security evolution of the kiosk-app's
LYSANDRA flight-deck: amber deck, violet reserved for privileged/destructive +
auth surfaces, teal telemetry, red alert, clearance chrome). A sibling of
serving/kiosk-app, kept in-repo for now (may graduate to its own submodule).
Three pillars over the manager's JSON API, plus the passkey gate:
- Login / Enrol — WebAuthn ceremonies (
navigator.credentials). Enrol is reached via the one-time link fromfleet-manager register-admin. - Monitor — fleet roster (online / version-drift / health) + per-host detail
with bespoke SVG telemetry charts (from
/api/hosts/{serial}/metrics). - Authorise — pending-enrolment queue: cross-check the fingerprint, approve (violet) + bind, or deny.
- Lifecycle — per-host desired-state (version pin, kiosk URL, reboot, drain); destructive changes are confirm-gated.
Build / embed
The built SPA is embedded into the fleet-manager binary via go:embed and
served same-origin over the admin plane.
npm ci
npm run build # -> dist/ (gitignored)
cd .. && go build -tags embedspa # embeds dist/ into the binary
The default go build (no tag) ships a stub instead, so Go builds/tests don't
require dist/. The Dockerfile does the two-stage build (npm → dist → go build
-tags embedspa).
Dev
npm run dev # Vite on :5173, proxies /api + /auth to :9500
Point it at a locally-running manager. Against an insecure+seeded manager
(FLEET_MGR_ADMIN_INSECURE=true FLEET_MGR_SEED=true), /api/whoami returns
dev-insecure, so the SPA renders the pillars without a passkey — handy for
theme/layout work. Passkey login/enrol need the manager in secure mode with a
valid RP origin + a WebAuthn authenticator.