lfg2025/archy
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases 33 Wiki Activity

feat: add container memory leak detection (MEM-02)

Browse Source 
MemoryTracker in health_monitor.rs tracks per-container RSS every 5 min.
Warns when a container's memory grows >50% over tracking period.
Parses podman stats output (GiB/MiB/KiB formats).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Dorian
2026-03-14 02:56:18 +00:00
parent e3e279331f
commit 952b7d1c92
2 changed files with 139 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
loop/plan.md
View File

@@ -243,7 +243,7 @@ Every test must pass **10 consecutive times** from BOTH .228→.198 AND .198→.
- [x] **MEM-01** — Added OOM-kill detection in disk_monitor.rs. `check_oom_kills()` runs `dmesg --level=err,crit` every 5 minutes, filters for "oom-kill" / "Out of memory" lines. New OOM kills logged via `warn!()` and written to `data_dir/oom-alert.json` for frontend consumption. Tracks last_oom_count to only alert on new events.
- [ ] **MEM-02** — Add container memory leak detection. Track per-container RSS over time in the monitoring collector. If a container's memory grows by >50% in 24h without corresponding workload increase, flag as potential leak. **Acceptance**: Monitoring page shows memory trend per container. Alert fires for simulated leak (container with growing allocation).
- [x] **MEM-02** — Added container memory leak detection in health_monitor.rs. MemoryTracker records per-container RSS samples every 5 minutes (288 samples max = 24h). check_leak() compares oldest vs newest sample — warns if growth > 50%. Uses `podman stats --no-stream` for live memory data. parse_memory_string() handles GiB/MiB/KiB formats.
- [x] **MEM-03** — Added disk growth alerting in disk_monitor.rs. Tracks 288 disk usage samples (24h at 5min intervals). Calculates daily growth rate from oldest→newest sample. Warns if growth > 1GB/day. 85% warning and 90% auto-cleanup with disk-warning.json already existed.