ServersCheck rule frequency doesn’t work

Are we doing something wrong?



Serverscheck v 7.8.3 Business (latest)



I am pinging a server with serverscheck.



Number of retries before rule fails? 3

Minimal interval between 2 checks: 300 (which is 5 mins)

Interval when status is down: 120



DOWN ALERT = Set check status to DOWN when Round Trip Time is > 5000ms





We get DOWN email after abt 1-2 minutes instead of 15 minutes. Red light on serverscheck also agrees with email. When email says its down, web monitor has red light.



The behavior has been like this through all versions of servers check we have used over the past 9 months or so. Rule frequency just doesnt seem to be adjustable.

Retry has always been immediate. The "interval when status is down" is the time interval between 2 DOWN checks and not between 3 DOWN? checks.

Sorry, I don't quite follow you.



So how do I tell serverscheck to not send DOWN alert unless the test server is down for 15 minutes? Preferably only testing abt 3 times in the 15 minute period.

Retries are done immediately; to alert "unless the test server is down for 15 minutes" is not possible.

Changed as follows...



Minimal interval between 2 checks: 300

Interval when status is down: 300





Still getting DOWN emails in two minutes.



So what do these settings do if they don't do what they say??



Minimal interval between 2 checks:

Interval when status is down:



I do not know that you understand me.



We want to do infrequent tests to not use up network bandwidth over wan.



I only want to check once every 5 minutes to Texas server. I don't want to test over and over again across the wan.



So, we want to test once every 5 minutes. If it fails aft 3 times, we would consider it down.



This software can't do that? Doesn't make sense...

I think you do not understand the difference between a DOWN status and a DOWN? status.



DOWN? is when a monitored system is not responding as expected. In order to avoid false alerts you can ask the software to perform a second, third, fourth knock. This is the famous retry. A retry is done as soon as the remote system did not answer correctly and as many times as you defined before sending an alert. At that point the status changes to DOWN



When a rule has a DOWN status it then waits the time as defined in "interval when status is DOWN" before performing the check again.



Hope this clarifies it.

It seems that you edited the post so I apologize for not having answered your last part. I hope my previous post clarifies it.



If not, then allow me to try it again:

Minimal interval between 2 checks -> this is the interval used between 2 checks when status is OK or WARNING



Minimal interval when status is DOWN -> this is the interval used when the rule status has been set to DOWN



Before a rule goes into DOWN state it first retries the number of times you defined:

OK->(interval between 2 checks)->DOWN? Retry 1->DOWN? Retry 2->DOWN? Retry 3->DOWN->(interval when status down)->OK

Greg,



Have you stopped/restarted monitoring since you changed the interval? I've had this problem before, where I change the interval but the old intervals remain in effect until I stop & restart the monitoring. You may want to try that.

I will try Jose... this is sorta nuts.

It might be nuts to you but this behavior has been like that since the start.



For one person the way the interval currently works is exactly what they want (it was implemented upon their request). For another one it may not be ideal. It is then a question of looking at what your requirement is.



Based on what I understood, you need a 3rd interval option whereby next to the number of retries you would enter the interval to be used for retries.



*UPDATE* Your requirement has been submitted as a feature enhancement request.

Feature is implemented in 7.8.4

Excellent - I was going to ask about this too.

Thank you!