Use this Knowledge Script to monitor CPU usage for the resource pool. This script raises an event when CPU usage exceeds the threshold. In addition, this script generates data streams for CPU usage in MHz. This script monitors and collects data for the following performance metric:
CPU usage - Sum of actively used virtual CPU of all powered on virtual machines in the resource pool.
NOTE:This script will not work with existing ResourcePoolCPUUsage jobs. As a result, you will need to start new ResourcePoolCPUUsage jobs after installing this release.
To enable the Knowledge Script to collect accurate CPU usage data for a resource pool, set the following Statistics Collection Intervals appropriately in the vCenter Management Server Configuration:
Collection Frequency: The interval duration in vCenter must be less than or equal to the AppManager job interval schedule. For example, if you run the VirtualCenter_ResourcePoolCPUUsage Knowledge Script at 15-minute intervals, the interval duration in vCenter must be less than or equal to 15 minutes.
For more information about setting the Interval Duration and Statistics Level the vCenter, see the VMware Virtual Infrastructure 3 documentation.
vSphere resource pool
vSphere virtual appliance (vApp)
By default, this script runs every 15 minutes.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Event Notification |
|
|
Raise event when CPU usage exceeds the threshold? |
Select Yes to raise an event if CPU usage exceeds the threshold you set. The default is Yes. |
|
Event severity when CPU usage exceeds the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which CPU usage exceeds the threshold. The default is 15. |
|
Raise event when CPU metrics are not available? |
Select Yes to raise an event if CPU metrics are not available. The default is Yes. |
|
Event severity when CPU metrics are not available? |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which CPU metrics are not available. The default is 15. |
|
Event severity when AppManager failed to get metrics |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager failed to retrieve metrics from vCenter. The default is 15. |
|
Event severity when AppManager failed to log in |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager failed to log in to vCenter. The default is 5. |
|
Event severity when ResourcePoolCPUUsage job fails unexpectedly |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the ResourcePoolCPUUsage job fails unexpectedly. The default is 5. |
|
Data Collection |
|
|
Collect data for CPU usage? |
Select Yes to collect data about CPU usage for charts and reports. The default is unselected. |
|
Monitoring |
|
|
Maximum threshold for CPU usage |
Specify the maximum amount of CPU usage that can occur before an event is raised. The default is 800 MHz. |