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.
- Entry intervals define the number of consecutive times a condition must be true before notification occurs. That is, if a condition is not true the specified number of times, no notification is generated.
- Exit intervals define the number of times, following the resolution of a condition, that the condition must be false before the notification is removed. That is, once notification is generated, it remains active until the condition causing the notification has disappeared for a specific number of intervals.