You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node memory/disk/load checks hardcoded warn=80%/crit=90% and reported
status on every single sample, so a transient spike (e.g. a backup job
briefly pushing memory over the line) flapped the check ok<->critical
repeatedly. Observed on k3s-node01 (base ~20%, brief 91% spikes -> 12
status transitions in one window) and a 4GB Pi sitting right at the
warning line.
- Expose MEM/DISK/LOAD warn+crit thresholds as env (chart values).
- Add FLAP_SAMPLES debounce: a new status is only reported after it
holds for N consecutive samples; until then the last reported status
is held. Symmetric (escalation and recovery both debounced), keyed
per check so memory/load/per-mount disk/per-device smart debounce
independently. State persists across loop iterations (pod lifetime).
- FLAP_SAMPLES defaults to 1 (no debounce = unchanged behavior);
raise to 3 to ride out transient spikes.
Chart bumped to 0.2.27.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments