Skip to main content

Standard Alarm Rule Templates

IPM includes standard templates for configuring alarm rules. These rules are triggered when certain conditions are met. You can use the standard rule templates to quickly identify and set up alarms based on common infrastructure error conditions.

IPM alarms derived from the standard set of rule templates operate in one of two ways:

  1. The majority of the rules will wait five minutes before executing their alarm queries using the data available in the system at that point in time. For legacy alarms this is generally a sufficient amount of time to ensure all data has arrived.

  2. A subset of the standard alarm rules (list follows) operate in a manner similar to Single Metric Alarms, where they trigger evaluation as data arrives in the system, allowing for a more immediate alarm triggering. Here there are two considerations:

    1. For entity types whose data comes from a single device or source, alarms will be evaluated within one minute of data arriving at the system.

    2. For entity types whose data could come from multiple sources (e.g., an Application entity with multiple host entities), alarms will be delayed by five minutes from the first observation of change plus additional time (up to a minute) for processing. Alarms will trigger immediately after the default delay or after all data arrives at the system, whichever comes first. Expiring previously triggered alarms will be evaluated based on available data. If new data arrives after an alarm has been triggered, the alarm rule will be re-evaluated using the latest data for the previous time interval. If re-evaluation results in triggering an alarm, an occurrence will be raised, even if the current occurrence has been cleared. If an alarm was already triggered and new data suggests the alarm is no longer required, it will not be cleared automatically.

    Standard alarm rule templates in this category:

    • ESX Host Max Memory State

    • Fabric Buffer-to-buffer Credits

    • Fabric Transmission Errors

    • Buffer-to-buffer Credits

    • Link Errors

    • Link Transmission Errors

    • Port Utilization

    • VM CPU Ready

There are four types of alarm rule templates to choose from.

Performance Alarm Rule Templates


Performance alarm rules monitor the performance of your infrastructure and alert you when issues like flow control, high read response time, latency, and vSAN congestion occur.

Health Alarm Rule Templates


Health alarm rules monitor the health of your infrastructure and alert you when issues like bad SCSI statuses, transmission errors, lost path errors, failed commands, and packet errors occur.

Capacity Alarm Rule Templates


Capacity alarm rules monitor the capacity of your infrastructure and alert you when issues like high CPU utilization, high or low port utilization, cache usage, or high memory utilization occur.