Change alarm settings and specify what actions are taken when the alarm is triggered. Take ownership of an issue by acknowledging the alarm.

The Datastore usage on disk alarm is one of the many default alarms included with vCenter Server. The alarm is enabled at installation. If the used disk space on the datastore exceeds 75 percent, the alarm triggers a Warning. If the used disk space on the datastore then exceeds 85 percent, the alarm triggers an Alert. These warnings and alerts appear in the user interface in the form of modified icons for the elements affected. To have the alarm perform actions beyond this visual notification, change the configuration of the alarm. Follow the workflow in the sample tasks in this example scenario to become familiar with changing the settings of an alarm and responding to a triggered alarm.

Changes that you can make to this alarm are altering the percentage values for a Warning and for an Alert, modifying the frequency of an alarm, and defining the action the system takes at an alarm. For this example, you lower the percentage values, but keep the default frequency. In addition, on the Actions tab, you configure the action so that the system sends an email to specified addresses when a condition triggers the alarm. Use the values shown in Values to Use in Changing the Settings of the Datastore Usage on Disk Alarm for making changes and configuring actions in the Alarm Settings dialog box.

Values to Use in Changing the Settings of the Datastore Usage on Disk Alarm

Item

Where Item Appears in the Interface

Value

Alarm name, Description, Alarm Type

In the Alarm Settings dialog box, click the General tab.

Keep default.

Warning

In the Alarm Settings dialog box, click the Triggers tab.

70

Alert

In the Alarm Settings dialog box, click the Triggers tab.

80

Range, Frequency

In the Alarm Settings dialog box, click the Reporting tab.

Keep default.

Action > Add Action

In the Alarm Settings dialog box, click the Action tab.

Send a notification email

Configuration

In the Alarm Settings dialog box, click the Action tab.

email_address_of_your_choice@your_organization.com

From normal to warning

In the Alarm Settings dialog box, click the Action tab.

Once

From warning to alert

In the Alarm Settings dialog box, click the Action tab.

Repeat

From alert to warning

In the Alarm Settings dialog box, click the Action tab.

Once

From warning to normal

In the Alarm Settings dialog box, click the Action tab.

Once

In the procedures for acknowledging and resetting triggered alarms, follow the steps described in the vSphere Client option for both.

1

You can view alarm settings from any object, but you can modify settings only through the object on which the alarm is defined. You create and modify alarms in the Alarm Settings dialog box.

2

You can specify the events, states, or conditions that triggers the alarm in the Triggers tab of the Alarm Settings dialog box. The options you choose under the General tab of the Alarm Settings dialog box determine the options available under the Triggers tab. An alarm definition must contain at least one trigger before it can be saved.

3

You can specify actions that the system performs when the alarm is triggered or changes status. You can enable and disable alarms and alarm actions independently of each other.

4

Acknowledging an alarm lets other users know that you are taking ownership of the issue. After an alarm is acknowledged, its alarm actions are discontinued. For example, a host has an alarm set on it that monitors CPU usage and that sends an email to an administrator when the alarm is triggered. The host CPU usage spikes, triggering the alarm which sends an email to the host's administrator. The administrator acknowledges the triggered alarm to let other administrators know he is working on the problem, and to prevent the alarm from sending more email messages. The alarm, however, is still visible in the system. Alarms are neither cleared, nor reset when acknowledged.

5

An alarm triggered by an event might not reset to a normal state if vCenter Server does not retrieve the event that identifies the normal condition. In such cases, reset the alarm manually to return it to a normal state.