For every host I configured a ping test and a number of other tests (service, disk space) that are dependant on the ping test. All the tests have an action profile that sends a mail on good and bad status.
The idea was that when the host goes down I only receive an alert mail for the ping and not for the dependant test. (Since the host is down, I don't need a mail to tell me a service is down)
However this doesn't work the way I expected.
When the dependant tests have
Condition=alive
Synchronize counters = on
Synchronize Status & alerts = off
And the host goes down, I get
a mail for all the dependant tests
no mail for the ping (this is unpredictable, sometimes I get a mail, sometimes I dont)
When the dependant tests have
Condition=alive
Synchronize counters = on
Synchronize Status & alerts = on
And the host goes down, I get
a mail for the ping
and a mail for all the dependant tests
Neither of these is wat I really wanted. I am doing something wrong?
Reducing the amount of mails sent
Re: Reducing the amount of mails sent
Yes, really very strange behaviour. What version of HM do you use?jdw wrote:When the dependant tests have
Condition=alive
Synchronize counters = on
Synchronize Status & alerts = off
And the host goes down, I get a mail for all the dependant tests
I think, it depends on conditions to start action parameter. Have you specified "Repeat 1 times", haven't it? It means you only get mail when status changed from Bad to Good or vice versa.jdw wrote:no mail for the ping (this is unpredictable, sometimes I get a mail, sometimes I dont)
Regards,
Yoorix
1) What version of HostMonitor do you use?
2) What value have you set for "Consider status of the master test obsolete after N seconds" option?
Option located on (Behaviour page in the Options dialog. 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.
If you set option to 2 sec, HostMonitor always will recheck Master test before checking depandant tests. However if you have a lot of master-dependant relations (thousands), it will effect performance.
Regards
Alex
2) What value have you set for "Consider status of the master test obsolete after N seconds" option?
Option located on (Behaviour page in the Options dialog. 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.
If you set option to 2 sec, HostMonitor always will recheck Master test before checking depandant tests. However if you have a lot of master-dependant relations (thousands), it will effect performance.
Regards
Alex
The version of hostmonitor is 5.92.
Master test obsolete is set to 300 seconds. Since most tests happen every 5 minutes, this seems like a good value.
I have about 1000 tests, most of them dependant on another test. Rechecking the master before every dependant check must have an impact on performance.
In the alert profile the condition for the mail is set to
- start when 1 consecutive bad results occur
- repeat 1 times
Master test obsolete is set to 300 seconds. Since most tests happen every 5 minutes, this seems like a good value.
I have about 1000 tests, most of them dependant on another test. Rechecking the master before every dependant check must have an impact on performance.
In the alert profile the condition for the mail is set to
- start when 1 consecutive bad results occur
- repeat 1 times