Data expiration

 

This topic describes how to supply the Data Expiration settings of a script-based alert definition.

For performance reasons and to support sensible business logic, alert definitions can include an expiration frequency for its alerts. Alert expiration prevents a new instance of an alert from being generated if the same set of conditions that generated the first alert occurs a second time within the period you specify. The behavior improves performance by preventing repeated evaluations of the same alert data. If the same set of conditions occurs after the expiration date of the first instance, a new instance of the alert is generated.

Certain key performance indicators need to be evaluated at a frequency that is sensible for the type of indicator. Data made available weekly is best evaluated at that same interval. In this case, hourly evaluation of the data is wasteful because the data change by the week and not by the hour. Similarly, important business decisions could be overlooked if alerts are not evaluated often enough. Equipment operating temperatures sampled hourly, for example, should be evaluated using an alert definition whose alerts expire hourly. Waiting a week to be notified about an out-of-range condition sampled hourly could be disastrous.

Use the Alert Expiration field to indicate this frequency. Choose a length of time closest to the frequency at which the data is sampled. Parent topic: Script-based alert definitions

---

Library | Support | Terms of use |

Last updated: Thursday, March 15, 2007 11:57am EST

This information center is powered by Eclipse technology. (http://www.eclipse.org)