Setting intervals and controlling oscillations

Information about the resources you are analyzing is gathered at specific intervals that are set when you create an evaluation definition.

You can set very short evaluation intervals, frequently updating your picture of the status of a system or program, or longer intervals, smoothing out your picture of the status of the system or program.

Although short intervals might give you a clearer picture of the dynamics of the attributes you are tracking, they consume more processor time than less frequent intervals. Depending on the condition being evaluated, however, you might want to have short intervals to ensure you are notified every time a given condition should occur. For example, you might want to be notified whenever a specific connection is out of service.

In other cases, you may receive an excessive number of notifications about nonrecurring conditions when using a short interval. To prevent this from happening, CICSPlex® SM uses entry and exit intervals to even out rapid activity oscillations, where:

For example, assume that a condition with a severity of HW (high warning) occurs. In order for this condition to cause notification to occur, you decide that the condition must remain true for two consecutive intervals. And the notification must remain in effect until the condition has been false for three consecutive intervals. Notice that the entry and exit intervals need not be the same.

[[ Contents Previous Page | Next Page Index ]]