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
Send SNMP Traps as an Alarm
The SNMP agent included with vCenter Server can be used to send traps when alarms are triggered on a
vCenter Server instance. The default hardware health alarms send SNMP traps by default.
Prerequisites
Ensure that vCenter Server SNMP agents and ESXi SNMP agents are properly configured.
Ensure that SNMP trap receiver agents are properly configured.
Required Privilege: Alarms.Create alarm or Alarms.Modify alarm
Procedure
1 On the Actions page of the alarm definition wizard, click Add.
2 In the Actions column, select Send a notification trap from the drop-down menu.
3 (Optional) Configure alarm transitions and frequency.
4 Click Finish to save the alarm settings.
SNMP Trap Notifications
The following table describes the information that is included in vCenter Server and ESXi trap notifications.
Table 4‑3. SNMP Trap Notification Details
Trap Entry Description
Type The state vCenter Server is monitoring for the alarm. Options include Host Processor (or CPU)
usage, Host Memory usage, Host State, Virtual Machine Processor (or CPU) usage, Virtual
Machine Memory usage, Virtual Machine State, Virtual Machine Heartbeat.
Name The name of the host or virtual machine that triggers the alarm.
Old Status The alarm status before the alarm was triggered.
New Status The alarm status when the alarm is triggered.
Object Value The object value when the alarm is triggered.
Run a Script or a Command as an Alarm Action
You can configure an alarm to run a script or a command in the vSphere Web Client when the alarm is
triggered.
Use the alarm environment variables to define complex scripts and attach them to multiple alarms or
inventory objects. For example, you can write a script that enters the following trouble ticket information
into an external system when an alarm is triggered:
n
Alarm name
n
Object on which the alarm was triggered
n
Event that triggered the alarm
n
Alarm trigger values
When you write the script, include the following environment variables in the script:
n
VMWARE_ALARM_NAME
n
VMWARE_ALARM_TARGET_NAME
n
VMWARE_ALARM_EVENTDESCRIPTION
vSphere Monitoring and Performance
114 VMware, Inc.