ASAP 3.0 QuickStart Guide

HP NonStop ASAP QuickStart Guide Page 28 of 35
GOAL CPU, BUSY < 90
This goal states that all CPUs on the system must be less than 90% busy. (Note: the best
way to read a goal is to mentally insert the words “must be” before the logical operator. So
in the case above, you would read it as “Busy MUST BE < 90”.)
When this goal is set ASAP will create an alert on ASAP Client when any CPU reaches 90%
busy or greater. It will also generate an EMS event if configured to do so.
Goals are hierarchical. You can set a goal for all CPUs like the one above, and then
override it with a more specific goal on individual CPUs. For example, these goals set a
90% busy goal for CPUs 1-4 and 6-16 and a 95% goal for CPU 5.
GOAL CPU, BUSY < 90
GOAL CPU 5, BUSY < 95
You can also set multiple goals in the same command:
GOAL CPU, BUSY < 90, QUEUE < 3, CHIT > 100
You can tell ASAP to create a critical or information EMS event when a goal is not being
met, in addition to the alert displayed on ASAP Client:
GOAL CPU, BUSY < 90 CRITICAL
GOAL CPU 5, BUSY < 95 INFO
By default, when ASAP creates an EMS event, it creates it for the first interval where the
problem was found. However, you can tell ASAP to continue to repeat the event until the
problem is corrected if you wish to do so:
GOAL CPU, BUSY < 90 CRITICAL REPEAT
You can also tell ASAP to use custom event numbers for the up and down events it writes.
Please see the ASAP Server Manual for more information on event generation.