Alarm actions are operations that occur in response to triggered alarms. For example, email notifications are alarm actions.

VMware provides a list of preconfigured actions you can associate with an alarm. These actions are specific to the object on which you set the alarm. For example, preconfigured alarm actions for hosts include rebooting the host and putting the host in maintenance mode. Alarm actions for virtual machines include powering on, powering off, and suspending the virtual machine.

Although the actions are preconfigured, you must manually set up certain aspects of the action, such as having the action occur when a warning is triggered or when an alert is triggered, and whether to repeat the action.

You can configure alarms to repeat. If you do, alarm actions are repeated at the specified interval (for example, every 10 minutes) until the alarm state changes or the alarm is acknowledged by the administrator

When an alarm is acknowledged, any repeated actions are suppressed. The alarm itself is not reset and remains in the same state until the triggering condition or state is no longer valid, or until an event is received that is configured to reset the state of the alarm.

Some alarm actions, such as sending notification emails or traps, and running a script, require additional configuration.


The default VMware alarms do not have actions associated with them. You must manually associate actions with the default alarms.