Hi
I have Cacti 0.8.7i, PIA 3.1 & Thold 4.9.3 installed on an Ubuntu box and a few test thresholds set up. Alerts are triggering fine on the Thold tab but I do not get the inital alert email for when the threshold has been breached. I do however get an email if the threshold continues to be breached after for example 5 minutes and also when the threshold has recovered.
Can anyone advise?
Thanks
No email alerts for inital threshold breach
Moderators: Developers, Moderators
Re: No email alerts for inital threshold breach
Can you turn on thold logging (in settings > Thold < Log Threshold Breaches) and then post the logs for when it happens?
If that doesn't give us anything useful, then you may have to turn on debug logging too.
If that doesn't give us anything useful, then you may have to turn on debug logging too.
Re: No email alerts for inital threshold breach
Hi
I have found that if I set the minimum trigger duration to 5 minutes rather than never that I get the emails fine, so I will just stick with that.
Another question though, I dont suppose there is a way to only send an email alert for the first time a threshold is triggered only? I say this because, in our network for example, some links may be at 9.5 GBPS and then they go to 9.4GBS followed by 9.5 GBS again which sends two emails as the threshold trigger is 9.5GB
Thanks
I have found that if I set the minimum trigger duration to 5 minutes rather than never that I get the emails fine, so I will just stick with that.
Another question though, I dont suppose there is a way to only send an email alert for the first time a threshold is triggered only? I say this because, in our network for example, some links may be at 9.5 GBPS and then they go to 9.4GBS followed by 9.5 GBS again which sends two emails as the threshold trigger is 9.5GB
Thanks
Re: No email alerts for inital threshold breach
You may want to try using Time Based alerts. They are exactly like Hi / Low but you set them up to only alert if the threshold is breached X times over the last Y minutes. It will then not count it as unbreached until it has gone below X breaches in Y minutes (its a floating time period). So one little dip below or above is not enough to set it off or reset it.
Who is online
Users browsing this forum: No registered users and 0 guests