Configuring vCenter Server to send alarms when virtual machines are running from snapshots
book
Article ID: 328627
calendar_today
Updated On:
Products
VMware
Issue/Introduction
This article provides information on configuring VMware vCenter Server to send alerts when virtual machines are running from snapshots.
Resolution
Prerequisites
Determine the level of the hierarchy you want to configure the alarm for.
The object hierarchy is vCenter > Datacenter > Cluster > Host(s) > Datastore > Folder > Resource Pool > Virtual Machine.
Alarms are inherited by all child objects.
Once configured you can see the alarm settings from the child objects but it is configurable only from the object where it was created.
To create alarms, the vSphere Client or vSphere Web Client must be connected to a vCenter Server with the appropriate user with permissions on all relevant objects. After an alarm is created, it is enabled even if the user who created it no longer has permissions.
To open the Alarm Settings dialog, perform one of these operations:
Right-click the object and click Alarm > Add Alarm.
In the Alarms tab, select the Definitions tab, right-click in the pane, and click New > Alarm.
Click on the object in the inventory and press Ctrl+A.
Alarm Settings – General tab
To create a new alarm:
Enter an alarm name and description.
Define the type of alarm:
In the Monitor list, click Virtual Machines.
Select Monitor for specific conditions or state.
Select Enable this alarm.
Alarm Settings – Triggers tab
State triggers are set off as soon as a state threshold or condition is achieved. You cannot define condition lengths for state alarms.
Note: You cannot use a virtual machine's Total Size on Disk or VM Snapshot Size triggers in combination with any other triggers.
To add a new alarm trigger:
Click Add.
In the Trigger Type dropdown, click VM Snapshot Size (GB).
In the On Condition dropdown, click Is above.
Double-click the Warning field and enter the desired value.
Double-click the Alert field and enter the desired value.
Define tolerance ranges and trigger frequencies for condition or state triggers.
Alarm Settings – Actions tab
To define an action:
Fill in the Configuration tab with the details required for the configured Action.
Select if you want the action to be executed with a specific frequency, or just when there is a status change from normal to warning, warning to alert, alert to warning, and warning to normal.
Click OK and the alarm is ready.
vSphere Web Client:
Log in to the vSphere Web Client with an administrative user.
Click Hosts and Clusters.
Right-click the object you want to add the alarm to.
Navigate to Alarms > New Alarm Definition...
Enter an alarm name and description.
Select the Monitor dropdown and click Virtual Machines.
Under Monitor for select specific conditions or state, for example CPU usage.
Select Enable this alarm.
Press Next.
Click Add.
In the Trigger Type dropdown, click VM Snapshot Size (GB).
In the Operator dropdown, click Is above.
Double-click the Warning Condition field and enter the desired value.
Double-click the Critical Condition field and enter the desired value.
Press Next.
Click Add.
Select the action you want to occur when the alarm is triggered.