kiosk-entryway ships metrics via vmagent (modules/hosts/nixos/kiosk-entryway/monitoring.nix) to VictoriaMetrics; kiosk-gene-desk only has bare prometheus.exporters.node with nothing scraping/shipping it anywhere.
Measured vmagent's actual footprint on entryway before filing this: ~30M RAM, <1% CPU steady-state - negligible next to chromium's own footprint on either host, so no performance concern blocking this.
Deferred out of the kiosk-hardware consolidation module (see that PR/commit) since it's a distinct concern from hardware/networking/user scaffolding - worth its own shared module (e.g. genebean.services.node-monitoring or similar) once there's time to design it properly, reusing the config.genebean.ports.node-exporter.port registry entry both hosts already reference.
🤖 Filed with Claude Code
kiosk-entryway ships metrics via vmagent (modules/hosts/nixos/kiosk-entryway/monitoring.nix) to VictoriaMetrics; kiosk-gene-desk only has bare prometheus.exporters.node with nothing scraping/shipping it anywhere.
Measured vmagent's actual footprint on entryway before filing this: ~30M RAM, <1% CPU steady-state - negligible next to chromium's own footprint on either host, so no performance concern blocking this.
Deferred out of the kiosk-hardware consolidation module (see that PR/commit) since it's a distinct concern from hardware/networking/user scaffolding - worth its own shared module (e.g. genebean.services.node-monitoring or similar) once there's time to design it properly, reusing the config.genebean.ports.node-exporter.port registry entry both hosts already reference.
🤖 Filed with Claude Code