Can anyone explain why this happens and even better, how I can surpress these clear messages?
Test with master test still produces clear messages
Test with master test still produces clear messages
I have lot's of services tests on our server. They all depend on the master test (ping server, "alive"). Still (for example when we reboot the server) all these dependent service tests give a clear error message. The raise messages are surpresses but the clear messages not.
Can anyone explain why this happens and even better, how I can surpress these clear messages?
Can anyone explain why this happens and even better, how I can surpress these clear messages?
What means "clear error message"? "raise messages"?
Does "clear error message" == "good action assigned to the test item"?
"raise messages" == "bad actions assigned to the test item"?
There is no difference in processing of "bad" and "good" actions in relation to master tests.
I think you just need to decrease value of "Consider status of the master test obsolete after N seconds" option (located on Behavior page in HostMonitor Options dialog).
Do not set too low value if you have a lot of master tests (e.g. 2 sec interval will be too short if you have 300 master tests). You may use Auditing Tool (menu View) to check if your new settings may lead to problems.
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. If Master test was performed more than N seconds ago, HostMonitor will recheck the Master test item before checking dependant items.
Please note: HostMonitor makes an exception for SNMP Trap test methods. If such test is used as Master test, its status never considered as obsolete. In other words status of Master SNMP Trap test will always be considered as up-to-date, regardless of the time when last trap message was received.
Regards
Alex
Does "clear error message" == "good action assigned to the test item"?
"raise messages" == "bad actions assigned to the test item"?
There is no difference in processing of "bad" and "good" actions in relation to master tests.
I think you just need to decrease value of "Consider status of the master test obsolete after N seconds" option (located on Behavior page in HostMonitor Options dialog).
Do not set too low value if you have a lot of master tests (e.g. 2 sec interval will be too short if you have 300 master tests). You may use Auditing Tool (menu View) to check if your new settings may lead to problems.
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. If Master test was performed more than N seconds ago, HostMonitor will recheck the Master test item before checking dependant items.
Please note: HostMonitor makes an exception for SNMP Trap test methods. If such test is used as Master test, its status never considered as obsolete. In other words status of Master SNMP Trap test will always be considered as up-to-date, regardless of the time when last trap message was received.
Regards
Alex