System Details - OS Test
This test collects various metrics pertaining to the CPU and memory usage of every processor supported by a VM.
Target of the test : A Proxmox Hypervisor
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for every combination of virtual machine
Parameter | Description |
---|---|
Test period |
How often should the test be executed. |
Host |
The IP address of the host for which this test is to be configured. |
Port |
The port at which the specified host listens. By default, this will be NULL. |
Proxmox Node Name |
Specify the name of the Proxmox node that you wish to monitor in this text box. By default, this parameter is set to none indicating that the test monitor all the nodes in the target hypervisor. |
Ignore VMs Inside View |
Administrators of some high security Proxmox environments might not have permissions to internally monitor one/more VMs. The eG agent can be configured to not obtain the 'inside view' of such ‘inaccessible’ VMs using the Ignore VMs Inside View parameter. Against this parameter, you can provide a comma-separated list of VM names, or VM name patterns, for which the inside view need not be obtained. For instance, yourIgnore VMs Inside View specification can be: *xp,*lin*,win*,vista. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside view of all VMs on a Proxmox Hypervisor by default. Note: While performing VM discovery, the eG agent will not discover the operating system of the VMs configured in the Ignore VMs Inside View text box. |
Ignore WINNT |
By default, the eG agent does not support the inside view for VMs executing on Windows NT operating systems. Accordingly, the Ignore WINNT flag is set to Yes by default. |
Exclude VMs |
Administrators of some virtualized environments may not want to monitor some of their less-critical VMs - for instance, VM templates - both from 'outside' and from 'inside'. The eG agent in this case can be configured to completely exclude such VMs from its monitoring purview. To achieve this, provide a comma-separated list of VMs to be excluded from monitoring in the Exclude VMs text box. Instead of VMs, VM name patterns can also be provided here in a comma-separated list. For example, your Exclude VMs specification can be: *xp,*lin*,win*,vista. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside and outside views of all VMs on a virtual host by default. By providing a comma-separated list of VMs/VM name patterns in the Exclude VMs text box, you can make sure the eG agent stops collecting 'inside' and 'outside' view metrics for a configured set of VMs. |
Domain, Admin User, Admin Password, and Confirm Password |
By default, this test connects to each virtual VM remotely and attempts to collect “inside view” metrics. In order to obtain a remote connection, the test must be configured with user privileges that allow remote communication with the virtual VMs. The first step towards this is to specify the Domain within which the virtual VMs reside. The Admin User and Admin Password will change according to the Domain specification. Discussed below are the different values that the Domain parameter can take, and how they impact the Admin User and Admin Password specifications:
|
Report By User |
While monitoring a Proxmox Hypervisor, the Report By User flag is set to No by default, indicating that by default, the VM operating systems on the target hypervisor are identified using the hostname specified in the operating system. On the other hand, if you want the desktops to be identified using the login of the user who is accessing them, set this flag to Yes. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename. |
Report Powered OS |
This flag becomes relevant only if the Report By User flag is set to ‘Yes’. If this flag is set to Yes (which is the default setting), then this test will report measures for even those VMs that do not have any users logged in currently. Such guests will be identified by their virtualmachine name and not by the username_on_virtualmachinename. On the other hand, if the Report Powered OS flag is set to No, then this test will not report measures for those VMs to which no users are logged in currently. |
Use Top for DD |
This parameter is applicable only to Linux VMs. By default, this parameter is set to No. This indicates that, by default, this test will report the detailed diagnosis of the Virtual CPU utilization measure for each processor on a Linux VM by executing the usr/bin/ps command. On some Linux flavors however, this command may not function properly. In such cases, set the Use Top for DD parameter to Yes. This will enable the eG agent to extract the detailed diagnosis of the Virtual CPU utilization measure by executing the /usr/bin/top command instead. |
Exclude |
Specify a comma-separated list of processor names / processor name patterns that you want to exclude from monitoring. |
CPU Utilization in Percent |
Specify the percentage of time beyond which the test should reveal the detailed diagnosis for the Virtual CPU utilization measure. By default, this parameter is set to 25. However, you can override this value as per your requirement. |
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 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:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Virtual CPU utilization |
This measurement indicates the percentage of CPU utilized by the processor. |
Percent |
A high value could signify a CPU bottleneck. The CPU utilization may be high because a few processes are consuming a lot of CPU, or because there are too many processes contending for a limited resource. The detailed diagnosis of this test reveals the top-10 CPU-intensive processes on the virtual machine. |
System usage of virtual CPU |
Indicates the percentage of CPU time spent for system-level processing. |
Percent |
An unusually high value indicates a problem and may be due to too many system-level tasks executing simultaneously. |
Run queue in VM |
Indicates the instantaneous length of the queue in which threads are waiting for the processor cycle. This length does not include the threads that are currently being executed. |
Number |
A value consistently greater than 2 indicates that many processes could be simultaneously contending for the processor. |
Blocked processes in VM |
Indicates the number of processes blocked for I/O, paging, etc. |
Number |
A high value could indicate an I/O problem on the VM (e.g., a slow disk). |
Swap memory in VM |
Denotes the committed amount of virtual memory. This corresponds to the space reserved for virtual memory on disk paging file(s). |
MB |
An unusually high value for the swap usage can indicate a memory bottleneck. Check the memory utilization of individual processes to figure out the process(es) that has (have) maximum memory consumption and look to tune their memory usages and allocations accordingly. |
Free memory in VM |
Indicates the free memory available. |
MB |
This measure typically indicates the amount of memory available for use by applications running on the target VM. On Unix operating systems (AIX and Linux), the operating system tends to use parts of the available memory for caching files, objects, etc. When applications require additional memory, this is released from the operating system cache. Hence, to understand the true free memory that is available to applications, the eG agent reports the sum of the free physical memory and the operating system cache memory size as the value of the Free memory in VM measure while monitoring AIX and Linux VM operating systems. |
Scan rate in VM |
Indicates the memory scan rate. |
Pages/Sec |
A high value is indicative of memory thrashing. Excessive thrashing can be detrimental to VM performance. |
Note:
For multi-processor systems, where the CPU statistics are reported for each processor on the system, the statistics that are system-specific (e.g., run queue length, free memory, etc.) are only reported for the "Summary" descriptor of this test.