When you post information about some problem, please include the following details: - OS version (e.g. Windows 2000 Professional SP3); HostMonitor version; problem description.
Besides: The amount even for 1000 tests that do not fail was nothing (zero, nada, nietschewo) because only failing tests are logged. It's your default setting to only log at status changes and midnight.
H'm, all settings are default with single Ping test... we cannot reproduce the problem.
Does HostMonitor perform this test within miliseconds?
please go to http://www.teamviewer.com/en/index.aspx download the setup (one can just run the program w/o installing) and have a look yourself.
ID is 228 780 102
Follow up to e-mail conversation (intermediary conclusion): so far we cannot confirm there is bug.
There is no problem with test items scheduled to be performed every second. Yes, in some cases (in most "real world" cases) HostMonitor may not perform such tests every second because test interval is interval between finish of test probe #N and start of test probe #(N+1). HostMonitor needs some time to perform the test, that's why you will not see Recurrences=60 after 60 sec of testing, even if you setup test to be performed every second.
That's how our software works from begining. Nothing changed.
We still trying to reproduce "5 sec interval" problem using your test list but so far everything works fine. Probably delay was related to low value specified for "Don't start more than [N] tests per second" option.
Auditing Tool displayed warning because specified value was below target test frequency.
You increased this counter, right? Does it work fine now?