| Measurement |
Description |
Measurement Unit |
Interpretation |
| Hypervisor_state |
Indicates the current state of the target hypervisor. |
|
The values this measure reports and their numeric equivalents are provided in the table below:
| Measure Value |
Numeric Value |
| Down |
0 |
| Up
| 1 |
Note:
By default, this measure reports the Measure Values listed in the table above. In the graph of this measure however, the current state of the hypervisor is indicated by its corresponding numeric equivalent only - i.e., 0 and 1.
The detailed diagnosis of this measure reveals the name of target hypervisor, the current state of the hypervisor, type, version and IP address of the hypervisor, details related to CPU, service ID of the hypervisor, etc. |
| Hypervisor_status |
Indicates whether/not the target hypervisor is enabled. |
|
A high value for this measure indicates that the memory resources are depleting drastically. Administrators may be alerted to add additional resources before memory resources are drained completely.
| Measure Value |
Numeric Value |
| Disabled |
0 |
| Enabled
| 1 |
Note:
By default, this measure reports the Measure Values listed in the table above. In the graph of this measure however, the current status of the hypervisor is indicated by its corresponding numeric equivalent only - i.e., 0 to 1. |
| Total_vcpu |
Indicates the total number of vCPUs in the target hypervisor. |
Number |
|
| Vcpu_used |
Indicates the number of vCPUs that are in use. |
Number |
|
| Vcpu_free |
Indicates the number of vCPUs that are available for use. |
Number |
A high value is preferred for this measure. |
| Vcpu_used_pct |
Indicates the percentage of the vCPUs used on the target hypervisor. |
Percent |
|
| Cells |
Indicates the number of cells on the target hypervisor. |
Number |
Cells functionality enables you to scale an OpenStack Compute cloud in a more distributed fashion without having to use complicated technologies like database and message queue clustering. Cells functionality supports very large deployments. |
| Sockets |
Indicates the number of sockets on the target hypervisor. |
Number |
With sockets, you can configure VMs entirely without networking. In such a case, communication will be allowed only though the sockets. |
| Cores |
Indicates the number of cores on the target hypervisor. |
Number |
Cores are connected by an interconnect to create a multi-core system, and have equal access to system resources like memory and input/output ports. |
| Threads |
Indicates the number of threads that can be used to run CPU processes on the target hypervisor. |
Number |
|
| Total_memory |
Indicates the total memory allocated for the target hypervisor. |
GB |
|
| Used_memory |
Indicates the amount of memory used on the hypervisor. |
GB |
The value of this measure should be low. |
| Free_memory |
Indicates the amount of memory available for use on the hypervisor. |
GB |
A high value is preferred for this measure. |
| Memory_usage |
Indicates the percentage of the memory used on the hypervisor. |
Percent |
|
| Total_local_storage |
Indicates the total amount of local disk storage on the target hypervisor. |
GB |
|
| Used_local_storage |
Indicates the amount of local storage used on the hypervisor. |
GB |
The value of this measure should be low. |
| Free_local_storage |
Indicates the amount of local storage available for use on the hypervisor. |
GB |
A high value is preferred for this measure. |
| Local_storage_usage |
Indicates the percentage of local storage used on the hypervisor. |
Percent |
|
| Current_workload |
Indicates the number of tasks that are currently handled by the hyervisor. |
Number |
This measure is a good indicator of the current workload of the hypervisor. |
| Running_vms |
Indicates the number of VMs that are currently running on the hypervisor. |
Number |
|