OPS-2 one-db: consolidate all whey telemetry/KPI sqlite into one local Postgres 17 db (telemetry), schema-per-domain, SELECT*-friendly views, reporting web UI. Goal: one place for all KPIs/perf/context data + Elazar can actually find/read them.

OPS-2 · agent-ops

one-db: consolidate all whey telemetry/KPI sqlite into one local Postgres 17 db (telemetry), schema-per-domain, SELECT*-friendly views, reporting web UI. Goal: one place for all KPIs/perf/context data + Elazar can actually find/read them.

ref	title	status	priority	assignee
OPS-3	one-db: lazy-load telemetry-inventory.md — single doc agents read on demand listing, per data stream: which systemd unit/timer/cron collects it, which script the unit runs, which table it writes, and which script reports to Elazar + which aro. Keep it the SSOT map of the whole telemetry pipeline.	canceled	high	bin-whey-cc
OPS-4	one-db: views layer — every table gets enough pg views (latest / daily / report rollups) so agents query a view with SELECT * (never name fields). Goal: zero token waste guessing columns. Document view list in telemetry-inventory.md.	canceled	high	bin-whey-cc
OPS-6	one-db: cutover (NO dual-write — Elazar dropped it 2026-06-06). Collectors write straight to pg via metrics_write (spools to JSONL on pg-down, so no data loss); backfill already loaded full history. Flip 5 collectors + netreport off sqlite, retire sqlite files once pg-proven.	canceled	high	bin-whey-cc
OPS-5	one-db: kpi.pensanta.com web UI on whey — small read-only server (chat-duo-web model, single-file .mjs) that reads the SELECT* views and renders KPI pages, so Elazar has one habit-friendly place to glance at all KPIs and drill into any metric when something looks off.	canceled	normal	coder-chatduo-cc

2026-06-06T03:38:50.893Z · q#46 · asked by wi-cli-whey → elazar · open

one-db source dir ~/Documents/terminal/one-db (schema.sql/00-role.sh/backfill.sh — not PATH scripts): make it its own git repo, or leave untracked working files? (still-open Q from before compact)

2026-06-06T03:38:19.812Z · created · wi-cli-whey
2026-06-06T03:38:50.893Z · questionAsked · wi-cli-whey

one-db source dir ~/Documents/terminal/one-db (schema.sql/00-role.sh/backfill.sh — not PATH scripts): make it its own git repo, or leave untracked working files? (still-open Q from before compact)
2026-06-06T03:40:30.966Z · canceled · wi-cli-whey

Dup of nw's dedicated one-db slug — canonical home is ONEDB-1..5. Superseded (PM call: dedicated slug cleaner than agent-ops). See ONEDB-*.