This test reports key metrics pertaining to the resource availability and resource usage of the RHEV server clusters managed by the RHEV manager.
Target of the Test: A RHEV Manager
Agent running the test: A remote agent
Output of the test: One set of results for each cluster in each datacenter configured on the RHEV manager being monitored.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port at which the specified host listens. The default port is 8443. |
|
RHEL MGR User and RHEL MGR Password |
To pull out the desired metrics from the RHEV manager, this test has to be configured with the privileges of a user who has been assigned the RHEVMUser role. Specify the user name and password of this user in the RHEL MGR User and RHEL MGR Password text boxes, respectively. |
|
Confirm Password |
Confirm the RHEL MGR Password by retyping it here. |
|
RHEL Manager Domain |
Specify the domain to which the RHEV manager belongs. By default, internal is displayed here. |
|
SSL |
If the RHEV manager to which the eG agent should connect is SSL-enabled, then set this flag to Yes. If not, set it to No. |
|
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
|
VMs powered on |
Indicates the number of VMs that are currently powered on in this cluster. |
Number |
|
||||||
|
VMs powered off |
Indicates the number of VMs that are currently powered off in this cluster. |
Number |
Use the detailed diagnosis of this measure to identify the powered off VMs in a cluster. |
||||||
|
VMs suspended |
Indicates the number of VMs in this cluster that are currently in a suspended state.
|
Number |
|
||||||
|
Other VMs |
Indicates the number of VMs in this cluster that are in an UNKNOWN state, are not responding, and are unassigned. |
Number |
Use the detailed diagnosis of this measure to know which VMs are in an UNKNOWN state, are not responding, and are unassigned. |
||||||
|
Max memory overcommitment |
Indicates the maximum percentage of memory this cluster is configured to over-commit. |
Percent |
Memory overcommitment, when configured at the cluster-level, allows the allocation of more virtual memory to the VMs in a cluster than the physical memory available to the hosts in the cluster.
|
||||||
|
Use thread as CPU |
Indicates whether this cluster has been configured to treat host CPU threads as cores. |
|
Clusters can be configured to treat CPU threads as cores for the purposes of virtual machine resource allocation and migration. The values this measure can report and their corresponding numeric values are listed below:
Note: By default, this measure reports the Measure Values listed in the table above to report the status of the ‘Use thread as CPU’ flag. In the graph of this measure however, this status is indicated using the numeric equivalents only. |
||||||
|
Total hosts |
Indicates the total number of hosts in this cluster. |
Number |
|
