Block a user
jupiter: add VictoriaMetrics monitoring
jupiter: add VictoriaMetrics monitoring
Review pass. The module evaluates clean on jupiter and checkConfig produces a validated checked-config derivation, so the scrape config is verified at build time. All five scrape targets do run node-exporter and tailscale, and the firewall reasoning in the header comment checks out (8428 is not in jupiter's allowedTCPPorts; trustedInterfaces is ["tailscale0" "lo"]).
jupiter: add VictoriaMetrics monitoring
With no scrape_timeout set, this inherits the 10s default — which is longer than the 5s interval. VictoriaMetrics resolves that by clamping the timeout down to the interval, so it silently becomes 5s.
jupiter: add VictoriaMetrics monitoring
This puts the TSDB on jupiter's eMMC, which I think is the one real blocker here.