OK message after Unknown status

[jcasares]

I don't remember since which version we started to get many OK notifications without an error notification first.
Analyzing them, they are all Unknown status we explicitly marked not to be taken as Bad.
How can we avoid the OK notifications in these cases? I see that there is an option on Alrt Profile that can tie it to a bad notification action. Will that work?

Unknown status is happening mostly when the HostMonitor remote agent does not reply, and we already have a test for that, but making them dependent doesn't solve the issue.

Thank you!

[KS-Soft]

Analyzing them, they are all Unknown status we explicitly marked not to be taken as Bad.
How can we avoid the OK notifications in these cases?

That's correct, Bad actions not started in this case, Good actions should be started.
If you need different behavior, you may use "advanced mode" good action, using expression like
('%SimpleStatus%'=='UP') and (%Recurrences%==1) and ('%LastSimpleStatus%'<>'UNKNOWN')

but making them dependent doesn't solve the issue

What settings did you set?
Options dialog
Recheck dependant test items when master test status has been changed
This option tells HostMonitor to recheck all dependant test items immediately after their master test failure or recovery (otherwise tests will be executed on regular schedule). This helps to maintain more accurate statistic information.
However HostMonitor does not "touch" dependant items when the master test changes its status to any of the "inactive" statuses (OutOfSchedule, WaitForMaster, Disabled, Paused). Unless next option is marked as well

Count inactive master test statuses as well
This option tells HostMonitor to change the statuses of all dependant tests when the Master test becomes inactive (OutOfSchedule, WaitForMaster, Disabled, Paused).

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