claude-memory/graph/solutions/health-check-escalation-logic-only-critical-severity-trigger-ad5a91.md

id	type	title	tags	importance	confidence	created	updated
ad5a911d-c7fa-4b7e-a488-17560c4067b3	solution	Health check escalation logic: only critical-severity triggers exit 2	monitoring claude-runner-monitoring python fix	0.8	0.8	2026-02-20T03:59:38.027169+00:00	2026-02-20T03:59:38.027169+00:00

In health_check.py, the original logic put ALL non-auto-remediable issues into the escalations list, triggering exit 2 (Claude invocation) even for minor warnings like load_high. Fixed by only adding issues with severity == "critical" to escalations. Warnings are still included in the JSON output but don't trigger Claude escalation. This prevents unnecessary API costs from load spikes on LXCs sharing a Proxmox host (gitea and uptime-kuma both report the host's load, which often exceeds 2-core thresholds).