▣ wi

ONEDB-2 · one-db · child of #697

No dual-write: cutover = flip reporter (netreport.sh) to pg + drop sqlite writes after parity. Per Elazar 2026-06-06.

Ref
ONEDB-2 (#698)
Project
one-db
Parent
backlog #697 one-db: 5 telemetry sqlite -> Postgres17 consolidation (umbrella)
Status
done
Priority
high
Type
task
Assigned
bin-whey-cc
Created by
wi-cli-whey
Created
2026-06-06T03:39:26.465Z
Updated
2026-06-06T21:03:12.635Z
Closed
2026-06-06T21:03:12.635Z

Sub-items (1/5 done · 20%)

reftitlestatuspriorityassignee
ONEDB-8 GATE#1 step i: add reporter-set pg views to schema.sql (network v_history/v_report/v_by_wifi; kpi 3-day window) — distinct from coder's dashboard views; back the 5 sqlite readers backlog high bin-whey-cc
ONEDB-9 GATE#1 step ii: repoint 5 sqlite readers to pg telemetry_ro — netreport.sh, testnetwork --report, ccusage-daily-kpi.sh, llmmsg-kpi-report.sh, memory-lint.sh backlog high bin-whey-cc
ONEDB-12 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 backlog high nw-whey-cc
ONEDB-10 GATE#1 step iii: flip venus-kpi-collect.sh to pg-write (telemetry_rw via metrics_write) — kills kpi.sqlite split-brain co-writer; nw lane (cross-host) blocked high nw-whey-cc
ONEDB-11 GATE#1 step iv: drop sqlite writes in 6 collectors after readers repointed+proven — pg-primary, JSONL-spool = resilience cache (Elazar: NO sqlite write-ahead). cc-context-monitor keeps LOCAL rolling cache for its own over-cap loop + pg mirror done high bin-whey-cc
+ Add sub-item

Questions

No questions.

Event log