Hi all,
- Two tests.
- - A (ping to 192.168.168.1)
- - B (Service xx on 192.168.168.1 is up).
- B depends on A to be up.
Both tests running every 15 minutes.
After a few days the tests will not be "time-syncron" I think.
Question:
Are both tests now (after a few days) running in there own 15 minute cycle. So when server is down test B may go down, because it was the first test that found out about the servers problem ?
Or is always running test A just before test B because of that dependency ?
Thanks
Juergen
Dependant tests. How does it work in detail ?
HostMonitor has a settings, which tells how long a 'master' test is valid. After this period, test A will be performed before test B is performed, regardless the previous state of test A.
Most likely you will perform test A much more than B. If you just want to test A and B and B being dependend on A, set the schedule for A much higher than B (at least twice as high).
Most likely you will perform test A much more than B. If you just want to test A and B and B being dependend on A, set the schedule for A much higher than B (at least twice as high).
From the help-file
"
Consider status of the master test obsolete after N seconds
This parameter is used by the program to determine whether the Master test status is up-to-date. Before starting a dependent test HostMonitor checks the status values of the Master tests defined on it. The parameter mandates for how long a Master test status is considered to be current.
"
And what if the master test is not current ? Is it retested before the depended test is done ?
"
Consider status of the master test obsolete after N seconds
This parameter is used by the program to determine whether the Master test status is up-to-date. Before starting a dependent test HostMonitor checks the status values of the Master tests defined on it. The parameter mandates for how long a Master test status is considered to be current.
"
And what if the master test is not current ? Is it retested before the depended test is done ?