This Knowledge Script is no longer supported as of AppManager for VMware vSphere version 7.7. It should not be used and should be deleted. The functionality of the script has been replaced by the following scripts: VmCPUUsage, VmMemoryUsage, VmDiskIO, and VmNetworkIO.
This script monitors and collects data for the following performance metrics:
CPU ready - Percentage of time the virtual machine was ready, but could not get scheduled to run on the physical CPU. CPU ready time depends on the number of virtual machines on the host and their CPU loads.
CPU usage - Amount of actively used virtual CPU, as a percentage of total available CPU.
CPU used - Total CPU usage.
CPU wait - Amount of CPU time spent in wait state.
Disk read rate (VM Disk IO) - Rate at which data is read from each virtual disk on the virtual machine.
Disk write rate (VM Disk IO) - Rate at which data is written to each virtual disk on the virtual machine.
Memory balloon - Amount of guest physical memory that is currently reclaimed from the virtual machine through ballooning. This is the amount of guest physical memory that has been allocated and pinned by the balloon driver.
Memory consumed - Amount of guest physical memory consumed by the virtual machine for guest memory. Consumed memory does not include overhead memory. It includes shared memory and memory that might be reserved, but not actually used.
Memory usage - Percentage of configured virtual machine “physical” memory usage.
Network data received - The rate at which data is received across the virtual machine’s vNIC (virtual network interface controller).Network data transmitted - The rate at which data is transmitted across the virtual machine’s vNIC (virtual network interface controller).Use the VmMonitor Knowledge Script rather than a combination of individual Knowledge Scripts to reduce system overhead.
NOTE:
CPU wait is a combined metric that includes CPU idle, CPU wait, and CPU halted. CPU wait is a defect in VMware. NetIQ Corporation is currently researching a solution with VMware (SR #1123183421). AppManager matches the value provided by VMware. For more information about this issue, see the VI SDK Release Notes at http://www.vmware.com/support/developer/vc-sdk/visdk-2.5.0-200711-releasenotes.html.
If the parent host of the monitored virtual machine is in maintenance mode, this Knowledge Script will not properly generate events.
Using this script and other VirtualCenter_Vm* scripts to monitor a large number of virtual machines at the same time might cause the jobs to fail. If the jobs fail on a regular basis, consider running the VirtualCenter_Vm* scripts on fewer virtual machines.
vCenter-monitored virtual machine
By default, this script runs every 15 minutes.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Event Notification |
|
|
CPU Notification |
|
|
Raise event when the percentage of CPU usage exceeds threshold? |
Select Yes to raise an event if the percentage of CPU usage exceeds the threshold. The default is Yes. CPU usage represents the percentage of CPU that was used during the monitoring interval. |
|
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 12. |
|
Raise event when the percentage of CPU ready time exceeds the threshold? |
Select Yes to raise an event if the percentage of CPU ready time exceeds the threshold. The default is Yes. |
|
Event severity when CPU ready time exceeds the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which CPU ready time exceeds the threshold. The default is 12. |
|
Raise event when the percentage of CPU wait time exceeds the threshold? |
Select Yes to raise an event if the percentage of CPU wait time exceeds the threshold. The default is unselected. |
|
Event severity when CPU wait time exceeds the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which CPU wait time exceeds the threshold. The default is 12. |
|
Raise event when the percentage of CPU used exceeds threshold? |
Select Yes to raise an event if the percentage of CPU used exceeds the threshold. The default is Yes. CPU used represents the percentage of time that CPU was used during the monitoring interval. |
|
Event severity when CPU used exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the amount of CPU used exceeds the threshold. The default is 12. |
|
Disk I/O Notification |
|
|
Raise event when disk reads exceed the threshold? |
Select Yes to raise an event if disk reads exceed the threshold. The default is Yes. |
|
Event severity when disk reads exceed the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which disk reads exceed the threshold. The default is 12. |
|
Raise event when disk writes exceed the threshold? |
Select Yes to raise an event if disk writes exceed the threshold. The default is Yes. |
|
Event severity when disk writes exceed the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which disk writes exceed the threshold. The default is 12. |
|
Memory Notification |
|
|
Raise event when the percentage of memory usage exceeds the threshold? |
Select Yes to raise an event if the percentage of memory usage exceeds the threshold. The default is Yes. Memory usage is a percentage of the total configured memory for a particular virtual machine. |
|
Event severity when memory usage exceeds the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which memory usage exceeds the threshold. The default is 12. |
|
Raise event when the percentage of memory consumed exceeds the threshold? |
Select Yes to raise an event if the percentage of memory consumed exceeds the threshold. The default is Yes. Memory consumed is the amount of host memory consumed by a virtual machine. |
|
Event severity when memory consumed exceeds the threshold. |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which memory consumed exceeds the threshold. The default is 12. |
|
Raise event when the percentage of memory balloon exceeds threshold? |
Select Yes to raise an event if the percentage of memory balloon exceeds the threshold. The default is Yes. |
|
Event severity when memory balloon exceeds the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which memory balloon exceeds the threshold. The default is 12. |
|
Network I/O Notification |
|
|
Raise event when network data received exceed the threshold? |
Select Yes to raise an event if network data received exceed the threshold. The default is Yes. |
|
Event severity when network data received exceed the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which network data received exceed the threshold. The default is 12. |
|
Raise event when network data transmitted exceeds the threshold? |
Select Yes to raise an event if network data transmitted exceeds the threshold. The default is Yes. |
|
Event severity when network data transmitted exceeds the threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which network data transmitted exceeds the threshold. The default is 12. |
|
Raise event when metrics are not available? |
Select Yes to raise an event if metrics are not available. The default is unselected. |
|
Event severity when metrics are not available |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which 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 CPU metrics from vCenter. The default is 15. |
|
Event severity when AppManager failed to log in |
Set the 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 VmMonitor job fails unexpectedly |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the VmMonitor job fails unexpectedly. The default is 5. |
|
Data Collection |
|
|
CPU Data Collection |
|
|
Collect data for average CPU usage? |
Select Yes to collect data for charts and reports on average CPU usage (amount of CPU used) for the host. The default is unselected. |
|
Collect data for individual CPU usage? |
Select Yes to collect data for charts and reports on CPU usage (amount of CPU used) for individual virtual machines. The default is unselected. |
|
Collect data for average CPU ready time? |
Select Yes to collect data for charts and reports on average CPU ready time for the host. The default is unselected. |
|
Collect data for individual CPU ready time? |
Select Yes to collect data for charts and reports on CPU ready time for individual virtual machines. The default is unselected. |
|
Collect data for average CPU wait time? |
Select Yes to collect data for charts and reports on average CPU wait time for the host. The default is unselected. |
|
Collect data for individual CPU wait time? |
Select Yes to collect data for charts and reports on CPU wait time for individual virtual machines. The default is unselected. |
|
Collect data for average CPU used? |
Select Yes to collect data for charts and reports on average CPU used (amount of time CPU was used) for the host.The default is unselected. |
|
Collect data for individual CPU used? |
Select Yes to collect data for charts and reports on CPU used (amount of time CPU was used) for individual virtual machines. The default is unselected. |
|
Disk I/O Data Collection |
|
|
Collect data for disk reads? |
Select Yes to collect data about disk reads in megabytes/sec for charts and reports. The default is unselected. |
|
Collect data for disk writes? |
Select Yes to collect data about disk writes in megabytes/sec for charts and reports. The default is unselected. |
|
Memory Data Collection |
|
|
Collect data for memory usage? |
Select Yes to collect data about memory usage for charts and reports. The default is unselected. |
|
Collect data for memory consumed? |
Select Yes to collect data about memory consumed for charts and reports. The default is unselected. |
|
Collect data for memory balloon? |
Select Yes to collect data about memory balloon for charts and reports. The default is unselected. |
|
Network I/O Data Collection |
|
|
Collect data for network data received? |
Select Yes to collect data about network data received for charts and reports. The default is unselected. |
|
Collect data for network writes |
Select Yes to collect data about network writes for charts and reports. The default is unselected. |
|
Monitoring |
|
|
CPU Monitoring |
|
|
Maximum threshold for average CPU usage |
Specify the maximum percentage of average CPU that can be used before an event is raised. The default is 80 percent. |
|
Maximum threshold for average CPU ready time |
Specify the maximum percentage of average CPU ready time that can occur before an event is raised. The default is 10 percent. |
|
Maximum threshold for average CPU wait time |
Specify the maximum percentage of average CPU wait time that can occur before an event is raised. The default is 10 percent. |
|
Maximum threshold for average CPU used |
Specify the maximum percentage of the average amount of time that CPU can be used before an event is raised. The default is 80 percent. |
|
Disk I/O Monitoring |
|
|
Maximum threshold for disk reads |
Specify the maximum megabytes of disk reads that can occur per second before an event is raised. The default is 1 megabytes/sec. |
|
Maximum threshold for disk writes |
Specify the maximum megabytes of disk writes that can occur per second before an event is raised. The default is 1 megabytes/sec. |
|
Memory Monitoring |
|
|
Maximum threshold for memory usage |
Specify the maximum percentage of memory usage that can occur before an event is raised. The default is 80 percent. |
|
Maximum threshold for memory consumed |
Specify the maximum percentage of memory that can be consumed before an event is raised. The default is 80 percent. |
|
Maximum threshold for memory balloon |
Specify the maximum percentage of memory balloon that can occur before an event is raised. The default is 2 percent. |
|
Network I/O Monitoring |
|
|
Maximum threshold for network data received |
Specify the maximum Mbits of network data received that can occur per second before an event is raised. The default is 1 Mbit/sec. |
|
Maximum threshold for network writes |
Specify the maximum Mbits of network writes that can occur per second before an event is raised. The default is 1 Mbit/sec. |