Files
pulse/internal
rcourtman cf365b5f80 fix: add default TimeThresholds to prevent hair-trigger alerts (fixes #491)
Root cause: NewManager() was missing TimeThresholds initialization, causing
all alert types to use 0-second delay. This meant alerts fired immediately
on the first sample exceeding threshold, with no debouncing.

Impact: LXC containers with brief CPU spikes to ~100% (normal for single-core
saturation) triggered constant alerts instead of only alerting on sustained
high CPU usage.

Fix: Add default TimeThresholds:
- guest: 10s delay (prevents alerts from brief CPU spikes)
- node: 15s delay
- storage: 30s delay
- pbs: 30s delay

This ensures CPU must stay above threshold for the configured duration
before an alert fires, preventing noise from momentary spikes.

Fixes #491
2025-10-02 11:31:56 +00:00
..
2025-10-01 19:24:20 +00:00