dborup 27628fbc3a feat: capture and chart SNR history per direct neighbor (#1865 follow-up) ...

dborup spotted the raw /neighbors payload also carries snr and
heard_secs_ago per neighbor -- previously dropped entirely by
handleNeighborsReport's parsing loop. Both fields are present regardless
of scope-query status (responded or timeout).

New append-only observer_neighbor_metrics table, inspired by the existing
RF Health tab's observer_metrics pattern: one row per neighbor per
/neighbors report, pruned on the same 30-day MetricsRetentionDays
schedule. Deliberately no ordering guard on the write side (unlike the
current-only observer_neighbors snapshot) -- every report is valid
history at its own timestamp.

GET /api/observers/{id}/neighbors/{pubkey}/metrics serves the raw
(undownsampled) history. Frontend renders a per-row SNR sparkline on the
Direct Neighbors panel using the same lightweight inline-SVG technique as
the RF Health grid's noise-floor sparklines (no Chart.js), loaded async
after the panel paints.

2026-07-26 19:21:54 +02:00

..

dbschema_test.go

perf(#1740): replace idx_tx_last_seen with partial index WHERE last_seen=0 (#1756)

2026-06-20 15:45:28 -07:00

dbschema.go

feat: capture and chart SNR history per direct neighbor (#1865 follow-up)

2026-07-26 19:21:54 +02:00

go.mod

fix(dbschema): canonical source for optional column migrations — fixes startup race (closes #1321) (#1322)

2026-05-23 08:33:21 -07:00

go.sum

fix(dbschema): canonical source for optional column migrations — fixes startup race (closes #1321) (#1322)

2026-05-23 08:33:21 -07:00