All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
* Set new test interval to 1 -- Starts when 1 consecutive Bad results occur.
* Send e-mail to team -- Starts when 2 consecutive Bad results occur.
* Send SMS to team -- Starts when 15 consecutive Bad results occur (M-F 8am-5pm)
* Send SMS to team -- Starts when 60 consecutive Bad results occur (Not M-F 8am-5pm)
Last weekend, our team received an SMS page for a device, about 78 minutes after it went down, but we expected to be notified at 60 minutes (since it was a weekend). I thought it was odd, until I realized that if I add up all the numbers above, that they add up to 78.
2 minutes test interval means 2 minutes between 2 events: test probe #N has been performed (finished) and test probe #N+1 has been started. If test requires about 15 sec to be performed, then probe #30 will be performed in 30*(2*60+15)-15=4035=67 minutes.
Thanks Alex. I had not taken into consideration how long it takes to perform the test. We are testing by sending 4 pings with 2000ms timeout, so worst case it would be 8 seconds? But if latency is low, 100ms, then it would take less than a second? If less than a second, then this doesn't really account for the delay. Let me see if I can remember where the logs are and try to look into this closer.
But if latency is low, 100ms, then it would take less than a second?
I thought we are talking about 30 consecutive "bad" results. No reply within 2000 ms to 4 packets = 8 seconds per test probe.
Let me see if I can remember where the logs are and try to look into this closer
You may enable "successful" and "failed" actions logging on "System Log" page in the Options dialog and check when exactly action was triggered. May be there is delay in GSM network.
If you are using HostMonitor version 7.00+, you may use Quick Log to check actions history