Now bad actions are being triggered on "Wait for master" statuses. And causes good actions to trigger when Status goes from "Wait for master" to "Ok"with a PreviousStatus of "Warning".
I do not want to enable "Tread unknown status as bad" because this will increment the dead counters instead of the unknown counters.
Since "Wait for master" produces an INKNOWN SimpleStatus this is expected behavior. I don't understand why.
In the manual for "Status groups' it reads:
Code: Select all
UNKNOWN INACTIVE
---------------------------------------
Unknown Disabled
Unknown host Wait for master
Out of schedule
Paused
Code: Select all
UNKNOWN
--------------------------------------
Unknown
Unknown host
Wait for master
Out of schedule
Paused
If this were the case, I could specify in my bad action "DOWN" and UNKNOWN" SimpleStatus. This would leave out "Wait for master", "Out of schedule" and "Paused" which would now have an INACTIVE SimpleStatus. The appropriate counters will be incremented between Down and Unknown SimpleStatus. In fact now you could add an INACTIVE counter as well. I don't know what use that would have bu I'm just saying. Most important you would not have to use "Treat unknown as bad" to trigger a bad action from an UNKNOWN SimpleStatus.
Now I am convinced that Alex is going to find something wrong with this. Maybe there is another way that I have not considered. In any case an INACTIVE SimpleStatus for those particular statuses seems like a good idea.
Regards