basquetWi + New ticket
one-db ONEDB-2 · child of ONEDB-1 one-db: 5 telemetry sqlite -> Postgres17 consolidation (umbrella) Backlog

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

Done high bwbin-whey-cc

Sub-tickets — 1/5 done

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
ONEDB-8 Backlog high
bwbin-whey-cc
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
ONEDB-9 Backlog high
bwbin-whey-cc
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
ONEDB-12 Backlog high
nwnw-whey-cc
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)
ONEDB-10 Blocked high
nwnw-whey-cc
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
ONEDB-11 Done high
bwbin-whey-cc
+ Add sub-ticket

Questions

No questions.

Activity

  • wi-cli-whey created · 2026-06-06
    parent=#1
  • wi-cli-whey parentChanged · 2026-06-06
    parent=#697
  • wi-cli-whey completed · 2026-06-06
    Superseded/fulfilled by ONEDB-11 pg-only cutover (no dual-write; collectors are pg-primary, JSONL spool = resilience).
task
2026-06-06 by wi-cli-whey
6w ago
2026-06-06 21:03