Installation guide

Table 21-8. Event Trigger Components
Trigger Component Description
Trigger type Event to monitor. Events can be generated by a user action or the system, for example,
Account Password Change and Alarm Email Sent.
Status The value that must be met for the alarm to trigger:
n
Normal
n
Warning
n
Alert.
Conditions Specifications that define the trigger.
Event conditions include the following components:
n
Argument – The event attribute to monitor.
n
Operator – The qualifier used to set the trigger value, for example Starts with and
Doesn’t start with.
n
Value – The value that must be met to trigger the event.
Conditions are not configurable for all events.
For example, you have a subset of hosts in the same datacenter named with the identifying prefix, QA_. To
trigger an alarm when any of these hosts lose network connectivity, create an alarm on the datacenter to monitor
the event Lost Network Connectivity. The trigger conditions are:
n
Argument — host.name
n
Operator — Starts with
n
Value – QA_
When storage connectivity is lost on a host named QA_Host1, the event triggers.
Event triggers do not rely on thresholds or durations. They use the arguments, operators, and values to identify
the triggering condition. When the triggering conditions are no longer true, a triggered alarm resets
automatically, and no longer triggers.
Virtual Machine Event Triggers
VMware provides preconfigured alarms that trigger when events occur on virtual machines.
Table 21-9 lists events you can use to trigger alarms on virtual machines.
Table 21-9. Virtual Machine Event Triggers
Event Category Available Events
Customization Customization started, Customization succeeded, Cannot complete Sysprep,
Unknown error.
Deployment VM created, VM auto renamed, VM being closed, VM being creating, VM
deploying, VM emigrating, VM hot migrating, VM migrating, VM reconfigured,
VM registered, VM removed, VM renamed, VM relocating, VM upgrading.
Cannot complete clone, Cannot migrate, Cannot relocate, Cannot upgrade.
DRS DRS VM migrated, VM powered on, No maintenance mode DRS recommendation.
Fault tolerance Secondary VM added, Secondary VM disabled, Secondary VM enabled, Secondary
VM started.
vCenter cannot start secondary VM, vCenter cannot update secondary VM
configuration, vCenter disabled fault tolerance.
Fault tolerance state changed, Fault tolerance turned off, Fault tolerance VM
deleted.
No compatible host for secondary VM.
Reached maximum Secondary VM (with FT turned On) restart count.
vSphere Basic System Administration
244 VMware, Inc.