The order in which rules are
evaluated has a large effect on the type of messages you receive.
It also affects the speed with which messages are sent and the
amount of processor time that is required by the policy.
For example, you might have a policy that monitors CPU activity,
containing these two rules:
If usage is greater than 80%,
send a warning message and stop processing rules.
If usage is greater than 95%,
send a critical message and stop processing rules.
If the rules were evaluated in the order shown, disk usage of 99%
would only produce a warning message. If the order were reversed,
however, a critical message would be sent. You could solve the
problem by making the rules more specific, so that the order was
not important:
If usage is between 80% and 94%,
send a warning message and stop processing rules.
If usage is greater than 95%,
send a critical message and stop processing rules.
In the example above, disk usage of 99% produces a critical message
regardless of which rule is evaluated first. However, if the rules
are evaluated in the order shown, disk usage of 99% is evaluated by
two rules. If the order were reversed, it would be evaluated only
by the first rule, thereby sending the message more quickly and
reducing processing time on the managed
node.
To change the rule order
Right-click the policy and select All TasksEdit...
Select a rule you want to move, and select Move Up or
Move Down.
Edit...