6.7
Table Of Contents
- vSphere Monitoring and Performance
- Contents
- About vSphere Monitoring and Performance
- 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
- Data centers
- Datastores and Datastore Clusters
- Disk Space (Data Counters)
- Disk Space (File Types)
- Disk Space (Datastores)
- Disk Space (Virtual Machines)
- Space Allocated by Datastore in GB
- Space Capacity by Datastore in GB
- 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 vSphere Health
- Monitoring Events, Alarms, and Automated Actions
- View Events
- View System Logs
- Export Events Data
- Streaming Events to a Remote Syslog Server
- Retention of Events in the vCenter Server Database
- View Triggered Alarms and Alarm Definitions
- Live Refresh of Recent Tasks and Alarms
- Set an Alarm in the vSphere Web Client
- Set an Alarm in the vSphere Client
- 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 Use 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
- View System Log Entries
- View System Logs on an ESXi Host
- System Logs
- Export System Log Files
- ESXi Log Files
- Upload Logs Package to a VMware Service Request
- Configure Syslog on ESXi Hosts
- Configuring Logging Levels for the Guest Operating System
- Collecting Log Files
- Viewing Log Files with the Log Browser
- Enable the Log Browser Plug-In on the vCenter Server Appliance
- Enable the Log Browser Plug-In on a vCenter Server Instance That Runs on Windows
- Retrieve Logs
- Search Log Files
- Filter Log Files
- Create Advanced Log Filters
- Adjust Log Times
- Export Logs from the Log Browser
- Compare Log Files
- Manage Logs Using the Log Browser
- Browse Log Files from Different Objects
n
Real-time statistics are collected on hosts and aggregated every 5 minutes. After six data points are
collected for approximately 30 minutes, they are rolled up to the vCenter Server database to create
the 1-Day statistic. 1-Day statistics might not be available for 30 minutes after the current time,
depending on when the sample period began.
n
The 1-Day statistics are rolled up to create one data point every 30 minutes. If a delay occurs in the
roll-up operation, the 1-Week statistics might not be available for 1 hour after the current time. It takes
30 minutes for the 1-Week collection interval, plus 30 minutes for the 1-Day collection interval.
n
The 1-Week statistics are rolled up to create one data point every two hours. If a delay occurs in the
roll-up operations, the 1-Month statistics might not be available for 3 hours. It takes 2 hours for the 1-
Month collection interval, plus 1 hour for the 1-Week collection interval.
n
The 1-Month statistics are rolled up to create one data point every day. If a delay occurs in the roll-up
operations, the statistics might not be available for 1-day and 3 hours. It takes one day for the past
year collection interval, plus 3 hours for the past month collection interval. During this time, the charts
are empty.
Solution
u
There is no solution available.
vSphere Monitoring and Performance
VMware, Inc. 115