Disk Activity - OS Test
This test reports statistics pertaining to the input/output utilization of each physical disk on a VM.
Note:
For this test to report measures on Linux VMs, the sysstat package must be installed on that VM (check for the existence of the iostat command on the target VM).
Target of the test : A Nutanix AHV server
Agent deploying the test : A remote agent
Outputs of the test : One set of results for every combination of virtual_guest:disk_partition or guest_user:disk_partition.
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. By default, this is NULL |
Prism Element IP |
If the eG manager had discovered the target Nutanix AHV server by connecting to the Nutanix Prism Element, then the IP address of the Nutanix Prism Element server used for discovering this Nutanix AHV server would be automatically displayed against the Prism Element IP parameter; similarly, the Prism Element User and Prism Element Password text boxes will be automatically populated with the Prism Element user credentials, using which Nutanix AHV discovery was performed. If this Nutanix AHV server has not been discovered using the Nutanix Prism Element, but you still want to monitor the Nutanix AHV server via the Prism Element, then select the IP address of the Prism Element server that you wish to use for monitoring the Nutanix AHV server from the Prism Element IP list. By default, this list is populated with the IP address of all Nutanix Prism Element hosts that were added to the eG Enterprise system at the time of discovery. Upon selection, the Prism Element user and Prism Element Password that were pre-configured for that Nutanix Prism Element will be automatically displayed against the respective text boxes. On the other hand, if the IP address of the Prism Element server of interest to you is not available in the list, then, you can add the details of the Prism Element server on-the-fly, by selecting the Other option from the Prism Element IP list. This will invoke the MANAGER DISCOVERY - VIRTUAL PLATFORM SETTINGS page. Refer to the Configuring eG Enterprise to Monitor Nutanix AHV |
Prism Element User, Prism Element Password and Confirm Password |
If the eG manager had discovered the target Nutanix AHV server by connecting to the Nutanix Prism Element, then the IP address of the Nutanix Prism Element server used for discovering this Nutanix AHV server would be automatically displayed against thePrism Element IP parameter; similarly, the Prism Element User and Prism Element Password text boxes will be automatically populated with the Prism Element user credentials, using which Nutanix AHV discovery was performed. If this Nutanix AHV server has not been discovered using the Nutanix Prism Element, but you still want to monitor the Nutanix AHV server via the Prism Element, then select the IP address of the Prism Element server that you wish to use for monitoring the Nutanix AHV server from the Prism Element IP list. By default, this list is populated with the IP address of all Nutanix Prism Element hosts that were added to the eG Enterprise system at the time of discovery. Upon selection, the Prism Element User and Prism Element Password that were pre-configured for that Prism Element server will be automatically displayed against the respective text boxes. On the other hand, if the IP address of the Prism Element server of interest to you is not available in the list, then, you can add the details of the Prism Element server on-the-fly, by selecting the Other option from the Prism Element IP list. This will invoke the MANAGER DISCOVERY - VIRTUAL PLATFORM SETTINGS page. Refer to the Configuring eG Enterprise to Monitor Nutanix AHV |
SSL |
By default, the Nutanix Prism Element server is SSL-enabled. Accordingly, the SSL flag is set to Yes by default. This indicates that the eG agent will communicate with the Prism Element server via HTTPS by default. |
WebPort |
By default, the Nutanix Prism Element server listens on port 9440. This implies that while monitoring a Nutanix AHV server via the Prism Element server, the eG agent connects to port 9440. |
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. |
Ignore VMs Inside View |
Administrators of some high security Hyper-V 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, your Ignore 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 Hyper-V host 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. |
Inside View Using |
By default, this test obtains the “inside view” of VMs using the eG VM Agent. Accordingly, the Inside view using flag is set to eG VM Agent by default. The eG VM Agent is a piece of software, which should be installed on every VM on a hypervisor. Every time the eG agent runs this test, it uses the eG VM Agent to pull relevant 'inside view' metrics from each VM. Once the metrics are collected, the eG agent then communicates with each VM agent and pulls these metrics, without requiring administrator privileges. Refer to Configuring the Remote Agent to Obtain the Inside View of VMs for more details on the eG VM Agent. |
Domain, Admin User, and Admin Password, and Confirm Password |
By default, these parameters are set to none. This is because, by default, the eG agent collects 'inside view' metrics using the eG VM agent on each VM. Domain administrator privileges need not be granted to the eG agent if it uses this default approach to obtain the 'inside view' of Windows VMs. |
Report By User |
While monitoring a Nutanix AHV server, the Report By Userflag is set to No by default, indicating that by default, the guest operating systems on the AHV server are identified using the hostname specified in the operating system. On the other hand, while monitoring AHV desktop environments, this flag is set to Yes by default; this implies that in case of VDI servers, by default, the guests will be identified using the login of the user who is accessing the guest OS. 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 thereport by user flagis set to ‘Yes’. If the Report Powered OS 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 Sudo |
This parameter is of significance to Linux and Solaris VMs only. By default, the USE SUDO parameter is set to No. This indicates that, by default, this test will report the detailed diagnosis for the Percent virtual disk busy measure of each disk partition being monitored by executing the /usr/bin/iotop command or /usr/sbin/iotop command. However, in some highly secure virtualized environments, this command cannot be executed directly on a Linux. In such cases, set this parameter to Yes. This will enable the eG agent to execute the sudo/usr/bin/iotop command or sudo/usr/sbin/iotop and retrieve the detailed diagnosis of the Percent virtual disk busy measure. |
Use IOTOP |
The Disk Activity – VM test uses the IOTOP command to collect detailed diagnostics on disk activity from Linux VMs. By default, this flag is set to No, indicating that the test will not use the IOTOP command – this in turn implies that this test will not report detailed diagnostics for Linux VMs by default. If you want the test to report detailed metrics on disk activity on Linux VMs, set this flag to Yes |
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 |
---|---|---|---|
Percent virtual disk busy: |
Indicates the percentage of elapsed time during which the disk is busy processing requests (i.e., reads or writes). |
Percent |
Comparing the percentage of time that the different disks are busy, an administrator can determine whether load is properly balanced across the different disks. |
Percent reads from virtual disk: |
Indicates the percentage of elapsed time that the selected disk drive is busy servicing read requests. |
Percent |
|
Percent writes to virtual disk: |
Indicates the percentage of elapsed time that the selected disk drive is busy servicing write requests. |
Percent |
|
Virtual disk read time: |
Indicates the average time in seconds of a read of data from the disk. |
Secs |
|
Virtual disk write time: |
Indicates the average time in seconds of a write of data from the disk. |
Secs |
|
Avg. queue for virtual disk: |
Indicates the average number of both read and write requests that were queued for the selected disk during the sample interval. |
Number |
|
Current queue for virtual disk: |
The number of requests outstanding on the disk at the time the performance data is collected. |
Number |
This measure includes requests in service at the time of the snapshot. This is an instantaneous length, not an average over the time interval. Multi-spindle disk devices can have multiple requests active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks. This difference should average less than two for good performance. |
Reads from virtual disk: |
Indicates the number of reads happening on a logical disk per second. |
Reads/Sec |
A dramatic increase in this value may be indicative of an I/O bottleneck on the guest. |
Data reads from virtual disk: |
Indicates the rate at which bytes are transferred from the disk during read operations. |
KB/Sec |
A very high value indicates an I/O bottleneck on the guest. |
Writes to virtual disk: |
Indicates the number of writes happening on a local disk per second. |
Writes/Sec |
A dramatic increase in this value may be indicative of an I/O bottleneck on the guest. |
Data writes to virtual disk: |
Indicates the rate at which bytes are transferred from the disk during write operations. |
KB/Sec |
A very high value indicates an I/O bottleneck on the guest. |
Disk service time: |
Indicates the average time that this disk took to service each transfer request ( i.e., the average I/O operation time) |
Secs |
A sudden rise in the value of this measure can be attributed to a large amount of information being input or output. A consistent increase however, could indicate an I/O processing bottleneck. |
Disk queue time: |
Indicates the average time that transfer requests waited idly on queue for this disk. |
Secs |
Ideally, the value of this measure should be low. |
Disk I/O time: |
Indicates the average time taken for read and write operations of this disk. |
Secs |
The value of this measure is the sum of the values of the Disk service time and Disk queue time measures. A consistent increase in the value of this measure could indicate a latency in I/O processing. |
The detailed diagnosis of the Percent virtual disk busy measure, if enabled, provides information such as the Process IDs executing on the disk, the Process names, the rate at which I/O read and write requests were issued by each of the processes, and the rate at which data was read from and written into the disk by each of the processes. In the event of excessive disk activity, the details provided in the detailed diagnosis page will enable users to figure out which process is performing the I/O operation that is keeping the disk busy. The detailed diagnosis for this test is available for Windows guests only, and not Linux guests.
Figure 1 : The detailed diagnosis of the Percent virtual busy measure