Condition and State triggers are comprised of a trigger type, a triggering condition and length, and warning and alert values.

Condition and State Trigger Components describes each component of Condition and State triggers.

Condition and State Trigger Components

Trigger Component

Description

Trigger type

The condition or state to monitor, for example, VM CPU Usage (%).

Condition

The qualifier used to set the threshold for the trigger, for example, Is Above and Is Below.

Warning

The value that must be reached for the alarm to transition from a normal state to a warning state, and to trigger the alarm.

Condition Length

For condition triggers, after the warning condition is reached, the amount of time the warning condition stays true in order for the warning to trigger.

State triggers do not have condition lengths. As soon as the state condition occurs, the warning is triggered.

Alert

The value that must be reached for the alarm to transition from the warning state to an alert state and to trigger the alarm.

Condition Length

For condition triggers, after the alert value is reached, the amount of time the alert condition stays true in order for the alarm to trigger.

State triggers do not have condition lengths. As soon as the state condition occurs, the alert is triggered.

For condition triggers to generate a warning or an alert, the value you set must be reached and for the specified condition length. For example, you can configure a condition trigger to generate a warning and an alert under the following conditions:

A virtual machine’s CPU usage must be above 75% for more than 10 minutes to generate a warning.

A virtual machine’s CPU usage must be above 95% for more than 5 minutes to generate a warning.

The 10 minute and 5 minute time conditions in this example help distinguish an erratic condition from a true scenario. You set time requisites to ensure that the metric conditions are valid and not caused by incidental spikes.

Triggered alarms reset when the triggering condition or state is no longer true. For example, if you have an alarm defined to trigger a warning when host CPU is above 75%, the condition will reset to normal when the value falls below the 75% and the warning alarm will no longer be triggered. The threshold condition is dependent on any tolerance range you set for the threshold.