Why is it that whenever I make a change to the logic of an alert the alert trigger that was altered fires off an alert for every check in my environment, for every defined component regardless of whether or not it is enabled and regardless of the state of the component (up, down, unmanaged, etc). Most recently I have a check that I defined as
Trigger Alert when all of the following apply
node name is equal to specifichostname01
trigger when any of the following apply
Application Name is equal to app1
Application Name is equal to app2
component status is not equal to Unknown
component status is not equal to Unmanaged
component status is not equal to Unreachable
this triggerd alerts for hosts that were not defined (ie nodename did not equal specifichostname01) for applications that were not one of the ones listed above and for components that were up, down, unmanaged, disabled in the template, etc. I never had this happen with any of the other server and application monitoring tools that I have used previously but for some reason this happens regularly with SAM. I would appreciate any suggestions on how to fix this and/or would like to suggest that the Devs get back to the drawing board on the alert engine.