6.0.1
Table Of Contents
- vSphere Monitoring and Performance
- Contents
- About vSphere Monitoring and Performance
- Updated Information
- Monitoring Inventory Objects with Performance Charts
- Performance Chart Types
- Data Counters
- Metric Groups in vSphere
- Data Collection Intervals
- Data Collection Levels
- View Performance Charts
- Performance Charts Options Available Under the View Menu
- Overview Performance Charts
- Clusters
- Datacenters
- Datastores
- Disk Space (Data Counters)
- Disk Space (File Types)
- Disk Space (Virtual Machines)
- Storage I/O Control Normalized Latency
- Storage I/O Control Aggregate IOPs
- Storage I/O Control Activity
- Average Device Latency per Host
- Maximum Queue Depth per Host
- Read IOPs per Host
- Write IOPs per Host
- Average Read Latency per Virtual Machine Disk
- Average Write Latency per Virtual Machine Disk
- Read IOPs per Virtual Machine Disk
- Write IOPs per Virtual Machine Disk
- Virtual Machine Observed Latency per Datastore
- Hosts
- Resource Pools
- vApps
- Virtual Machines
- CPU (%)
- CPU Usage (MHz)
- Disk (Average)
- Disk (Rate)
- Disk (Number)
- Virtual Disk Requests (Number)
- Virtual Disk Rate (KBps)
- Memory (Usage)
- Memory (Balloon)
- Memory (Swap Rate)
- Memory (Data Counters)
- Network (Usage)
- Network (Rate)
- Network (Packets)
- Disk Space (Data Counters)
- Disk Space (Datastores)
- Disk Space (File Types)
- Fault Tolerance Performance Counters
- Working with Advanced and Custom Charts
- Troubleshoot and Enhance Performance
- Monitoring Guest Operating System Performance
- Monitoring Host Health Status
- Monitoring Events, Alarms, and Automated Actions
- View Events
- View System Logs
- Export Events Data
- View Triggered Alarms and Alarm Definitions
- Live Refresh of Recent Tasks and Alarms
- Set an Alarm
- Acknowledge Triggered Alarms
- Reset Triggered Event Alarms
- Preconfigured vSphere Alarms
- Monitoring Solutions with the vCenter Solutions Manager
- Monitoring the Health of Services and Nodes
- Performance Monitoring Utilities: resxtop and esxtop
- Using the vimtop Plug-In to Monitor the Resource Usage of Services
- Monitoring Networked Devices with SNMP and vSphere
- Using SNMP Traps with vCenter Server
- Configure SNMP for ESXi
- SNMP Diagnostics
- Monitor Guest Operating Systems with SNMP
- VMware MIB Files
- SNMPv2 Diagnostic Counters
- System Log Files
- Index
Table 4‑4. Alarm Environment Variables (Continued)
Variable Name Variable Description Supported Alarm Type
VMWARE_ALARM_TRIGGERINGSUMMARY A multiline summary of the
alarm.
Condition, State, Event
VMWARE_ALARM_DECLARINGSUMMARY A single-line declaration of the
alarm expression.
Condition, State, Event
VMWARE_ALARM_ALARMVALUE The value that triggered the
alarm.
Condition, State
VMWARE_ALARM_EVENTDESCRIPTION A description of the alarm status
change event.
Condition, State
VMWARE_ALARM_EVENTDESCRIPTION A description of the event that
triggered the alarm.
Event
VMWARE_ALARM_EVENT_USERNAME The user name associated with
the event.
Event
VMWARE_ALARM_EVENT_DATACENTER The name of the data center in
which the event occurred.
Event
VMWARE_ALARM_EVENT_COMPUTERESOURCE The name of the cluster or
resource pool in which the event
occurred.
Event
VMWARE_ALARM_EVENT_HOST The name of the host on which
the event occurred.
Event
VMWARE_ALARM_EVENT_VM The name of the virtual machine
on which the event occurred.
Event
VMWARE_ALARM_EVENT_NETWORK The name of the network on
which the event occurred.
Event
VMWARE_ALARM_EVENT_DATASTORE The name of the datastore on
which the event occurred.
Event
VMWARE_ALARM_EVENT_DVS The name of the vSphere
Distributed Switch on which the
event occurred.
Event
Alarm Command-Line Parameters
VMware provides command-line parameters that function as a substitute for the default alarm environment
variables. You can use these parameters when running a script as an alarm action for a condition, state, or
event alarm.
The command-line parameters enable you to pass alarm information without having to change an alarm
script. For example, you can use these parameters when you have an external program for which you do not
have the source. You can pass in the necessary data by using the substitution parameters, which take
precedence over the environment variables. You pass the parameters through the Configuration dialog box
in the alarm definition wizard or on a command line.
Table 4‑5. Command-Line Parameters for Alarm Action Scripts
Variable Description
{eventDescription} The text of the alarmStatusChange event. The {eventDescription} variable
is supported only for Condition and State alarms.
{targetName}
The name of the entity on which the alarm is triggered.
{alarmName}
The name of the alarm that is triggered.
{triggeringSummary}
A summary of the alarm trigger values.
{declaringSummary}
A summary of the alarm declaration values.
vSphere Monitoring and Performance
116 VMware, Inc.