Looking for a duration threshold

[vik-patel]

i.e. only alert if CPU is above 80% for 5 mins

[rcourtman]

this is already supported. go to Alerts > Thresholds > scroll down to "Alert Delay (seconds before triggering)"

there are separate delay settings for VMs/Containers, Nodes, Storage, and PBS. set the delay in seconds (e.g., 300 for 5 minutes) and alerts will only trigger after the threshold has been exceeded for that duration

[vik-patel]

Ok thx! … I suggest changing “seconds before triggering” to “seconds above threshold before triggering” in the GUI to make it clearer On Sep 30, 2025, at 11:51 AM, rcourtman ***@***.***> wrote: this is already supported in the alert configuration you can set duration thresholds per resource type in the alert settings. for example, to only alert if CPU is above 80% for 5 minutes: { "timeThresholds": { "guest": 300, "node": 60, "storage": 30, "pbs": 60 } } the values are in seconds. when a threshold is exceeded, pulse starts tracking it and only fires the alert after the duration has been met you can configure this in the alert settings under the advanced section —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[vik-patel]

After setting threshold duration to 10min I'm still seeing alerts with "0m" duration ... bug?

[rcourtman]

Thanks for flagging this. I found that alert durations were being reset when the delay threshold expired, which is why you still saw 0m. The fix is merged into main (69cc3aa) and will ship in the next release. Appreciate the heads up!

[vik-patel]

@rcourtman can you have a look at this again ... I'm NOT seeing alert email anymore (v4.21.0)... I've set the threshold for VM & Nodes to 1 sec ... I do see a bunch of resolved alerts in the history all with 0m duration

[vik-patel]

I take that back ... looks to be working ... I set the threshold to low and alerts fired ... thx for the fixes!