Hi
We have a monitor policy that uses a single rule that says if any of the PXE services is not running on a DS server send us a critical alert. This rule basically says if this service is not running or this other service in not running etc. then set the alert to critical. We then say to reset the rule status using an updated metric, which we take to mean when the non running services within the rule that caused the alert return to a running state.
When we test this though the alert is triggered but immediately resolves itself and we cannot see why. We suspect this because one of the subsequent service state tests within the rule returns a 'running' and this is therefore deemed to be metric update. However this would be a little odd if this were the case, as it would not be considering the rule results overall (any failure in the rule equals overall failure)
Has anyone encountered anything similar or can shed any light on this? We are wondering if this may be a bug as surely this is not how these rules are supposed to work?
All thoughts and feedback gratefully received!!
Cheers
Steve