Hi there,
I am wondering about the order the conditions of actions get evaluated. I have an action that gets triggered only with MySQL problems with a condition on a tag names "service" and a value of "mysql".
That works fine but I still the other admins get notifications on MySQL problems because that pre-defined action has no conditions at all. Of course I could take the above condition and add it negated to the default action. But assuming I am adding more actions and conditions I would always need to add the negated conditions to the default action. Is there any way around this? Or maybe I just didn't really understand how it works.
Also is there a specific order in how the actions (and their associated conditions) are processed? For instance it would be nice to be able to "bail out" of processing on a specific condition) (just as in processing Apache rewrite rules).
Thanks in advance.
I am wondering about the order the conditions of actions get evaluated. I have an action that gets triggered only with MySQL problems with a condition on a tag names "service" and a value of "mysql".
That works fine but I still the other admins get notifications on MySQL problems because that pre-defined action has no conditions at all. Of course I could take the above condition and add it negated to the default action. But assuming I am adding more actions and conditions I would always need to add the negated conditions to the default action. Is there any way around this? Or maybe I just didn't really understand how it works.
Also is there a specific order in how the actions (and their associated conditions) are processed? For instance it would be nice to be able to "bail out" of processing on a specific condition) (just as in processing Apache rewrite rules).
Thanks in advance.