|
Measures reported by ProxHypNodeTest
The test auto-discovers the nodes in the target Proxmox Hypervisor and, for each node, reveals the current status. Additionally, the test reports the total CPU and memory capacity allocated to each node, and accurately pinpoints the node on which the memory and CPU resources have been over-utilized. This way, the test warns administrators of a probable resource contention on each node.
Outputs of the test :One set of results for each node in the Proxmox Hypervisor being monitored
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Status |
Indicates the current status of this node. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
| Measure Value |
Numeric Value |
| Online |
1 |
| Offline |
0 |
Note:
By default, this measure reports the above-mentioned Measure Values while indicating the state of a node. In the graph of this measure however, the state is indicated using the numeric equivalents only. |
| Tot_mem |
Indicates the total amount of memory allocated to this node. |
GB |
|
| Use_mem |
Indicates the amount of memory used by this node. |
GB |
Ideally, the value of this measure should be much lesser than the value of the Total memory measure. If the value of this measure is equal to or is rapidly approaching the value of the Tot measure, it means that the node is running out of memory resources. |
| Free_mem |
Indicates the amount of memory available for use in this node. |
GB |
Ideally, the value of this measure should be high. |
| Mem_utilize |
Indicates the percentage of memory utilized by this node. |
Percent |
A value close to 100% is indicative of excessive memory usage by a node, and signals a potential memory contention on the node. |
| Max_cpu |
Indicates the minimum number of CPU guaranteed to this node. |
Number |
|
| Cpu_usage |
Indicates the percentage of CPU used by this node. |
Percent |
A value close to 100% is indicative of excessive CPU usage by a node, and signals a potential CPU resource contention on the node. |
| Up_time |
Indicates the total time that this node has been up since its last reboot. |
Seconds |
This measure displays the number of years, months, days, hours, minutes and seconds since the last reboot. Administrators may wish to be alerted if a node has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions. |
|