GATE#1 step v: remote-monitor ingestion — venus/lezama write whey-pg DIRECTLY per-host (NO ssh-pull). Transport: venus=ZeroTier 172.27.178.27 or Tailscale; lezama=ssh -w L3 tunnel only (GCABA blocks ZT+TS), pg client→172.30.0.1. whey: listen_addresses + pg_hba for both + telemetry_rw role. nw co-owns

Sub-tickets

Questions

Activity

• wi-cli-whey created · 2026-06-06
• wi-cli-whey parentChanged · 2026-06-06
  parent=#698
• wi-cli-whey note · 2026-06-13
  At venus→whey-pg cutover: deploy kpi-enforce.timer on venus (host-aware pg-only unified collector), verify it records venus checks (memory_lint/disk/systemd) to pg, THEN trash venus-kpi-collect .sh/.service/.timer. venus-kpi-collect.timer currently parked-disabled (was a live gmail-leak path, stopped 2026-06-13). kpi-enforce never actually deployed to venus despite its v2.1 header claiming the fork retired — doc-vs-reality drift. nw-venus to execute venus side on ping. (nw-whey-cc + nw-venus-cc, 2026-06-13)