serversdownandClaude Opus 4.8 ad6071b790 fix(alerts): reset rule state + close open event on rule edit/delete ...

invalidate() only dropped the rule cache, not the per-(unit,rule) state machine —
so editing a rule's metric/threshold left a stale 'active' phase that mis-evaluated
against the new config (spurious clear, or suppressed onset), and deleting an
in-alarm rule left an open AlertEvent that kept the client portal stuck "in alarm"
forever. update/delete now call _reset_rule_runtime: forget_rule() drops the state
machine and any open event for that rule is closed.

Verified: existing evaluator tests + cooldown scenario still pass; compiles.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-11 23:40:52 +00:00

..

__init__.py

initial scaffold

2025-12-23 18:22:55 +00:00

alerts.py

fix(alerts): reset rule state + close open event on rule edit/delete

2026-06-11 23:40:52 +00:00

background_poller.py

feat: monitor heartbeat + background poller skips active-monitored units

2026-06-09 17:33:29 +00:00

database.py

initial scaffold

2025-12-23 18:22:55 +00:00

device_logger.py

Add:

2026-01-29 18:50:47 +00:00

main.py

feat: persistent monitor_enabled flag + auto-start keepalive on boot

2026-06-09 19:27:25 +00:00

models.py

feat: downsampled DOD trail + history endpoint for live-chart backfill

2026-06-09 19:58:30 +00:00

monitor.py

feat(monitor): adaptive poll rate, unreachable backoff, device-offline alert

2026-06-10 06:47:20 +00:00

routers.py

fix(alerts): reset rule state + close open event on rule edit/delete

2026-06-11 23:40:52 +00:00

services.py

perf: monitor caches run state, ~halving live-feed latency

2026-06-09 18:52:13 +00:00