I have the latest versions of everything and have also installed the latest Thold plugin but have a small question. As a test, I am simply monitoring traffic_in bits per second on one port of a switch and have configured a simple alert to test threshold breaks.
After the threshold breaks, the threshold is shown as currently triggered in red. My question is when the condition normalizes by decreasing traffic below the threshold, it takes much longer - aproximately 20mins - before the alert is shown as not triggered.
The actual graph displays the correct "below threshold" condition after the next poll but the current value in the Thresholds tab takes around 3 or 4 more polls before they are similar.
I am sure there is a config reason for this but I can't see it anywhere. Can someone enlighten me please?
Thanks in advance.
Tue Jan 10, 2006 4:10 pm
jimmy
Site Admin
Joined: Thu Nov 11, 2004 11:12 am Posts: 2007
What do you have set as the "Trigger Count" for the threshold? I would also assume that baseline thresholding is turned off, as it can cause issues like this.
Tue Jan 10, 2006 4:40 pm
kramsay
New User
Joined: Thu Jan 05, 2006 4:56 pm Posts: 9
Hi Jimmy
"Default Trigger Count" in Alerting/Thold Settings is set for 1 . (There is only one place this is set yes?). All other setting are templated at also 1.
Baseline alerting is set to off in the device template..
I have also deleted and recreated the threshold and graph just in case but still the same issue.
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
