6.5.1
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)
- 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
- 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
- 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
- Index
6
Enable or disable the vpxd.event.syslog option.
The default value for the seing is enabled.
Retention of Events in the vCenter Server Database
You can congure vCenter Server to retain events in the database for a limited period. Discarding events
periodically ensures optimal performance of the database.
In new installations of vCenter Server 6.5, the event clean up option is enabled by default and the default
number of days to retain event messages in the database is 30. You can change this value to the number of
days that you want to retain the event messages in the database.
If you are upgrading or migrating from vCenter Server 6.0 or earlier, and you had the event cleanup option
enabled, your seing to retain events is preserved after the upgrade or migration to
vCenter Server Appliance 6.5.
After the retention period ends, the events are deleted from the database. However, there might be latency
in the deletion of the events that are older than the congured retention seing.
Configure Database Settings
You can congure the maximum number of database connections that can occur simultaneously. To limit the
growth of the vCenter Server database and save storage space, you can congure the database to discard
information about tasks or events periodically.
N Do not use the database retention options if you want to keep a complete history of tasks and events
for your vCenter Server.
Procedure
1 In the vSphere Web Client, navigate to the vCenter Server instance.
2 Select the tab.
3 Under , select General.
4 Click Edit.
5 Select Database.
6 In Maximum connections, type a number.
Increase this number if your vCenter Server system performs many operations frequently and
performance is critical. Decrease this number if the database is shared and connections to the database
are costly. Do not change this value unless one of these issues pertains to your system.
7 Select the Enabled check box next to Task cleanup to have vCenter Server periodically delete the
retained tasks.
8 (Optional) In Tasks retained for, type a value in days.
Information about tasks that are performed on this vCenter Server system is discarded after the
specied number of days.
9 Select the Enabled check box next to Event cleanup to have vCenter Server periodically clean up the
retained events.
10 (Optional) In Events retention, type a value in days.
Information about events for this vCenter Server system is discarded after the specied number of days.
11 Click OK.
vSphere Monitoring and Performance
108 VMware, Inc.