6.5.1

Table Of Contents
Monitoring Events, Alarms, and
Automated Actions 4
vSphere includes a user-congurable events and alarms subsystem. This subsystem tracks events happening
throughout vSphere and stores the data in log les and the vCenter Server database. This subsystem also
enables you to specify the conditions under which alarms are triggered. Alarms can change state from mild
warnings to more serious alerts as system conditions change, and can trigger automated alarm actions. This
functionality is useful when you want to be informed, or take immediate action, when certain events or
conditions occur for a specic inventory object, or group of objects.
Events
Events are records of user actions or system actions that occur on objects in vCenter Server or on a host.
Actions that might be recorded as events include, but are not limited to, the following examples:
n
A license key expires
n
A virtual machine is powered on
n
A user logs in to a virtual machine
n
A host connection is lost
Event data includes details about the event such as who generated it, when it occurred, and what type of
event it is. There are three types of events:
n
Information
n
Warning
n
Error
In the vSphere Web Client, event data is displayed in the Monitor tab. See “View Events,” on page 105.
Alarms
Alarms are notications that are activated in response to an event, a set of conditions, or the state of an
inventory object. An alarm denition consists of the following elements:
n
Name and description - Provides an identifying label and description.
n
Alarm type - Denes the type of object that is monitored.
n
Triggers - Denes the event, condition, or state that triggers the alarm and denes the notication
severity.
n
Tolerance thresholds (Reporting) - Provides additional restrictions on condition and state triggers
thresholds that must be exceeded before the alarm is triggered. Thresholds are not available in the
vSphere Web Client.
VMware, Inc.
103