ONEDB-12 ·
one-db · child of #698GATE#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
- Ref
ONEDB-12(#744)- Project
one-db- Parent
- done #698 No dual-write: cutover = flip reporter (netreport.sh) to pg + drop sqlite writes after parity. Per Elazar 2026-06-06.
- Status
- backlog
- Priority
- high
- Type
- task
- Assigned
- nw-whey-cc
- Created by
- wi-cli-whey
- Created
- 2026-06-06T13:11:50.537Z
- Updated
- 2026-06-06T13:11:55.308Z
Questions
No questions.
Event log
-
parent=#698
-
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)