I am having trouble making a certain set of conditions work and wanted to see if someone might have a suggestion.
So the scenario is that I am using a customer Advanced Alert Rule, not the delivered alert rule, to monitor up/down status of a node. The trigger conditions are working fine but I am having an issue with the reset conditions. Rather than just checking for the Node Status to be Up, I am checking the following:
Reset Alert when all of the following apply:
Node Status is not equal to Unknown
Node Status is not equal to Down
Node Status is not equal to Warning
I was doing this because I did not want the alert to reset if the Node Status was either Up, Unmanaged or Unreachable. This was working fine. However now I have decided that I don't want triggered alerts to reset if the Node Status is Unreachable.
To provide an example, let's consider a dependency with Node01 as the Parent and Node02 as the child. To start, Node02 is Down but Node01 is Up. Then Node01 goes down and Node02 goes to Unreachable. I don't want Node02's triggered alert to Reset which it does do with the above conditions. Instead I want the alert on Node02 to remain in force.
In other words, when Node01 comes back up, I still want Node02 to be triggered and then the situation with Node02 can be re-evaluated on the next poll. But I don't want Node02's pre-triggered alert to reset just because Node01 joined the list of down nodes and is it's Dependent Parent.
One would think that I could just add Unreachable to the list above making the new list read:
Reset Alert when all of the following apply:
Node Status is not equal to Unknown
Node Status is not equal to Down
Node Status is not equal to Warning
Node Status is not equal to Unreachable
However when I configure the conditions this way, the alert for Node01 does not reset when it comes back up. Of course, then when Node02, which is still down, also comes back up, its alert also does not reset.
Can anyone explain to me why that is?