I think this wish have been posted before, but it here it comes again.
If test C fails, and it is dependent on test B which is dependent on test A, today it is likely that all 3 tests will make an alert.
My suggestion is if a test fail, all master tests should be tested and then, as in the caseabove, test A should fail, and test B and C should be "Wait for Master"
Will this be possible ?
Regards
Sven
Master tests
No, alert will be triggered by test C only.If test C fails, and it is dependent on test B which is dependent on test A, today it is likely that all 3 tests will make an alert.
If master test fails, it could trigger alerts for all or some dependant tests. This behavior depends on settings, see "Synchronize Status&Alerts" option.
I think new option will be added in version 5.My suggestion is if a test fail, all master tests should be tested and then, as in the caseabove, test A should fail, and test B and C should be "Wait for Master"
On the other hand if you set "Consider status of the master test obsolete after 2 seconds" option (Behavior page in the Options dialog), HostMonitor will work exactly as you want.
Regards
Alex
Hi Alex,KS-Soft wrote: I think new option will be added in version 5.
On the other hand if you set "Consider status of the master test obsolete after 2 seconds" option (Behavior page in the Options dialog), HostMonitor will work exactly as you want.
Regards
Alex
what are the consequences when setting "Consider status of the master test obsolete after 2 seconds".
Example:
You have a master test and 30 dependant tests with different schedules
I think that will lead to 60 tests (the master will likely be rechecked with every of the dependent tests)
If that is true, I'll vote for the new feature as described above by Wooltown
... and requested by others
http://www.ks-soft.net/cgi-bin/phpBB/vi ... php?t=1315
http://www.ks-soft.net/cgi-bin/phpBB/vi ... php?t=2875
Not necessarily 60 tests because HostMonitor may perform 10-100 tests in these 2 seconds. However short interval will lead to some increase in system load, for surewhat are the consequences when setting "Consider status of the master test obsolete after 2 seconds".
Example:
You have a master test and 30 dependant tests with different schedules
I think that will lead to 60 tests (the master will likely be rechecked with every of the dependent tests)
Regards
Alex
andKS-Soft wrote:However short interval will lead to some increase in system load, for sure
... unnecessary log entries of master tests ? (don't know exactly)
... more load on WAN connections
I'll try lowering the "Consider status of master test obsolete after x seconds" from the default 300 and see what will happen.
I'll start with 30 seconds.
Many thanks for your response
Juergen
Maybe I've set that manually and can't remember 