Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1.

Alarm persistence

Alarm persistence provides the ability to handle or ignore short-lived data anomalies or data spikes.

For example, if a data element like CPU usage spikes up temporarily and exceeds an alarm threshold, you may not want to generate an alarm report immediately. Persistence give you the ability to wait and see if the condition persists for multiple evaluation periods.

During alarm definition evaluation, MainView Alarm Management not only compares the MainViewproduct data to your threshold values, it also evaluates the results against a desired persistence level. For example, you can elect to generate an alarm report only when the value exceeds a threshold for a specified number of times out of a specified sample size. You may only want to generate an alarm report when an evaluation exceeds a threshold 3 out of 5 times.

Related topic

Alarm-Management-terms-and-concepts

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*