feat(m8): event-based alerts — Xid/OOM/MCE/PCIe/disk from the kernel log — 0.34.0 #28

Merged

jessey merged 4 commits from feat/event-alerts into main 2026-05-22 12:48:42 +00:00

Conversation 0 Commits 4 Files Changed 9

+130 -11

4 Commits

Author	SHA1	Message	Date
jessey	3b1a2e7393	Merge branch 'feat/event-alerts' of ssh://jesseyvanofferen.com:2222/jessey/rigdoctor into feat/event-alerts	2026-05-22 14:42:53 +02:00
jesseyandClaude Opus 4.7	2989e8e23e	ci: run tests.yml on pull_request only (no push) to avoid double runs ... A branch with an open PR triggered both the push and pull_request events, running every job twice. Trigger on pull_request only; pushes to main are already tested by release.yml's `test` job. No version bump (CI config only). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 14:42:41 +02:00
jessey	670df23e06	Merge branch 'main' into feat/event-alerts	2026-05-22 12:41:34 +00:00
jesseyandClaude Opus 4.7	2ee7763d00	feat(m8): event-based alerts — Xid/OOM/MCE/PCIe/disk from the kernel log — 0.34.0 ... AlertMonitor now scans the kernel log (journalctl -k) every ~30s and fires one-shot, cooldown-gated desktop alerts on critical events: NVIDIA Xid, OOM kills, CPU machine-checks, PCIe AER, and disk I/O errors — so users are warned the moment something goes wrong, not only on a temperature threshold. Disk I/O errors come from the kernel log (no root needed, unlike smartctl). Edge/spam protection reuses the existing cooldown model. syslogs.scan_critical() does the matching; init seeds last-scan to "now" so old boot logs don't alert on launch. Tests for the matcher + monitor gating/cooldown; Settings note updated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 14:41:13 +02:00