fix: persistent state — uptime, status, latency, and logs survive restarts #13

2026-05-16T19:27:18Z

lerko commented

2026-05-16 19:27:18 +00:00

Summary

Uptime percentage now computed from windowed statuses (last 60 checks), not unbounded counters
Status and latency seeded from last DB record on startup (no more all-PENDING after restart)
Logs persisted to DB table, loaded on startup (last 100 entries)
Logs auto-pruned to 200 rows

Test plan

go test ./... passes
Restart app — status shows UP/DOWN immediately, not PENDING
Restart app — Logs tab shows previous session entries
Simulate a failure — uptime percentage drops visibly within the check window

## Summary - Uptime percentage now computed from windowed statuses (last 60 checks), not unbounded counters - Status and latency seeded from last DB record on startup (no more all-PENDING after restart) - Logs persisted to DB table, loaded on startup (last 100 entries) - Logs auto-pruned to 200 rows ## Test plan - [x] `go test ./...` passes - [ ] Restart app — status shows UP/DOWN immediately, not PENDING - [ ] Restart app — Logs tab shows previous session entries - [ ] Simulate a failure — uptime percentage drops visibly within the check window

lerko added 3 commits 2026-05-16 19:27:19 +00:00

fix(tui): compute uptime from windowed statuses, not running counters 52c85b11b8

fix: seed status and latency from DB history on startup 4d375cf874

feat: persist logs to DB, load on startup ed082e4080

lerko merged commit fa1042a2ec into develop

2026-05-16 19:27:24 +00:00

lerko referenced this issue from a commit

2026-05-16 19:27:25 +00:00

Merge pull request 'fix: persistent state — uptime, status, latency, and logs survive restarts' (#13) from fix/uptime-percentage into develop

Sign in to join this conversation.