First time with advanced alerts

[sherrera]

I have 3 ping tests in 1 folder that I have been trying to do some advanced alerts on. To make sure I am doing the syntax correctly I renamed the tests to test1, test2, test3. So my alert look like:

('%::test1::SimpleStatus%'=='DOWN') and ('%::test2::SimpleStatus%'=='DOWN') and ('%::test3::SimpleStatus%'=='DOWN')

I reverse the alerts to make them fail on purpose, nothing happens. So I try them 1 by 1 to see if that works.

('%::test1::SimpleStatus%'=='DOWN') works by itself and ('%::test3::SimpleStatus%'=='DOWN') works by itself but ('%::test2::SimpleStatus%'=='DOWN') will not work by itself. I tried a copy of test1 and changed the name to test4 and changed the alert to ('%::test4::SimpleStatus%'=='DOWN') and that will not work. I created a test 4 from scratch, that does not work.

Basically test1 and test3 will work for me, but not test2 or any new test I make. This is my first time working with advanced alert but it seems changing testname should be straight forward to test if syntax is correct.

I have HM 6.10 on W2k3 SP1.

Thanks for any help.

[KS-Soft Europe]

('%::test1::SimpleStatus%'=='DOWN') and ('%::test2::SimpleStatus%'=='DOWN') and ('%::test3::SimpleStatus%'=='DOWN')

The syntax seems to be correct.

I reverse the alerts to make them fail on purpose, nothing happens.

Have you set such action up into "Bad status action" set or into "Good status action"?

So I try them 1 by 1 to see if that works.
('%::test1::SimpleStatus%'=='DOWN') works by itself and ('%::test3::SimpleStatus%'=='DOWN') works by itself but ('%::test2::SimpleStatus%'=='DOWN') will not work by itself.

So, you have set up advanced action ('%::test2::SimpleStatus%'=='DOWN') for test "test2" and it does not work, when test returns "bad" status? Did you disable "Reverse alert" option for that test? Have you set such action up into "Bad status action" group?

Regards,
Max

[KS-Soft]

Could you send your configuration files to support@ks-soft.net?
We need actions.lst, hostmon.ini and .HML file (test list)

Regards
Alex

[sherrera]

Test3 is the only one that has the alerts. I have only tried the alerting from test3.

I check and uncheck the reverse alert to make it go bad and then good again to keep testing it.

The test is in bad status action group, and I do not move it. I only change the syntax of the test names to test the different tests.

[sherrera]

Sorry,
I was replying while you posted that. I will send the files.

[KS-Soft]

Test3 is the only one that has the alerts. I have only tried the alerting from test3

Then action should be executed right after test3 was performed (if all 3 test items shows "bad" status)

Regards
Alex

[sherrera]

Test3 is the only one that has the alerts. I have only tried the alerting from test3

Then action should be executed right after test3 was performed (if all 3 test items shows "bad" status)

Regards
Alex

I agree alex, but if it will never alert for test2 then the alert will never happen based on all 3. I hope that makes sense.

[KS-Soft]

Max tested your configuration and sent e-mail to your address.
I just write conclusion here:

Probably action is not executed by HostMonitor because
1) you have assigned action profile to test3 only
2) you are using Refresh button to force HostMonitor to recheck test items and HostMonitor starts all 3 tests at the same time.
If test3 finished while test1 or test2 still in "checking" state, action will not be triggered because %SimpleStatus% variable is not equal to 'DOWN' (status=checking, SimpleStatus=Unknown').
Solution? If you assign alert profile to all tests, it will be executed.

BTW: I assume you do not want to receive e-mail after each probe. If you need e-mail when all 3 tests become "bad", use expression like ('%::test1::SimpleStatus%'=='DOWN') AND ('%::test2::SimpleStatus%'=='DOWN') AND ('%::test3::SimpleStatus%'=='DOWN') and ((%::test1::Recurrences%==1) or (%::test2::Recurrences%==1) or (%::test3::Recurrences%==1))

Regards
Alex

[sherrera]

Thank you Max and Alex. All is working fine now.