Similarly, the "MBS 100 < 200" Range Count for write I/O operations reflects the number of one-second intervals during which the hIOmon I/O Monitor actually observed a total amount of data transferred by write I/O operations that was 100 000 000 bytes (i.e., 100 megabytes) or more, but less than 200 000 000 bytes (i.e., 200 megabytes).

The hIOmon "Disk I/O Ranger Display" is included within the:

• The hIOmon "Wordload I/O Profiler (WIOP)", which is an installed software package that is provided upon a subscription-fee basis.  It supports both the historical display of summarized I/O operation metrics (which are retrieved from supported hIOmon Manager Export Files or from Microsoft® "Event Tracing for Windows (ETW)" log files) as well as the display of real-time metrics captured by the ETW.

  The WIOP features a configuration script that can completely automate the configuration of the hIOmon software.  By default, the script specifies that the operating-system physical disk associated with the system drive Logical Disk (typically the C: logical drive) is to be monitored by the hIOmon software.  The configuration script can also be manually run so that you can explicitly specify another (or one or more other) Logical Disks whose associated physical disks are to be monitored by the hIOmon software.

  In addition, the script automatically configures the hIOmon software so that three distinct types of Comma-Separated-Values (CSV) hIOmon Manager Export Files are created and activated:

  • One type of hIOmon Manager Export File will contain the summary device I/O metrics for the physical disks being monitored
  
  
  • A separate type will contain a variety of "Data Transfer Size (DTS)" summary metrics for the physical disks being monitored.  These DTS metrics reflect I/O operation activity observed by the hIOmon I/O Monitor for I/O operations whose data transfer size/length was that of the corresponding size/length.
  
  
  • The third type will contain summary I/O metrics for each individual process instance that has its respective I/O operations performed by the physical disks being monitored

  The WIOP version provides you with an extremely simple, quick and easy way to both collect and display the unique hIOmon Performance Threshold Range Metrics upon a specific overall physical device and process basis.

• The hIOmon "Workload I/O Profiler Files (WIOPF)", which is also an installed software package that is provided upon a subscription-fee service basis.  Like the WIOP, it supports both real-time and historical displays of the collected summarized I/O operation metrics; it also includes the WIOP automated configuration script that you can optionally use to configure the hIOmon software.

  In addition, the WIOPF version allows you to explicitly specify the particular files that are to be monitored by the hIOmon software.  This additional configuration option enables you to restrict the monitoring of I/O operations to specific files rather than solely upon an overall device basis.

• The hIOmon REST API software package.  This software package features the "On-the-Web (OTW)" version of the hIOmon Disk I/O Ranger Display.  This version is "online/Internet-based" and runs within a supported Web Browser.   It allows you to use the hIOmon Disk I/O Ranger Display without having to install the software upon your computer.

  The hIOmon Disk I/O Ranger Display OTW version effectively enables you to connect to a remote computer in a secure fashion to use the hIOmon Disk I/O Ranger Display software that is installed upon that computer.

The hIOmon "Performance Threshold Range Metrics" provide a quick and easy way to assess the actual "speeds and feeds" I/O performance of your particular files, devices and applications in everyday, normal usage!

The hIOmon "Disk I/O Ranger Display" also supports the display of the hIOmon "DataTransferred/Time Index (DXTI)" metric, which provides a "high-level" means for relative comparison of I/O performance, where basically "higher is better".

That is, the "higher" the DXTI number, the better the performance - as in more data transferred and/or less required response time (i.e., application wait).  It resembles the "fuel economy" index for an automotive vehicle (i.e., "miles-per-gallon" or "kilometres/litre") as an overall measure of "performance efficiency".

The installed hIOmon "Disk I/O Ranger Display" software included with the hIOmon WIOP and hIOmon WIOPF runs as a Microsoft Windows HTML Application (HTA).  See the sections immediately below for specific installation and configuration requirements.

Installation Information

NOTE that the following section pertains only to the hIOmon "Workload I/O Profiler (WIOP)":

The hIOmon WIOP software is provided within a software installation package file, either the "hIOmonInstall32.exe" file (for 32-but operating systems) or the "hIOmonInstall64.exe" file (for 64-bit operating system).  Simply run the software installation package, which will invoke the standard Windows Installer that will perform the actual installation of the hIOmon software.  Administrator privileges are required to perform the installation process, which typically takes just a few minutes to complete.

Please note that during this installation process, you will need to:

• Agree to the hyperI/O LLC "End-User Software License Agreement (EUSLA)"

• Enter the specific "serial number" that you received from hyperI/O LLC for installing the hIOmon software

• Select whether you simply want to monitor and collect I/O operation metrics for the operating-system physical disk associated with the system drive (typically the C: Logical Disk); this is the default option.  You can instead select to explicitly specify one or more Logical Disks whose associated physical disks are to be monitored.  Note that you can later use the configuration Settings "Reconfigure" option to modify which particular physical disks are to be monitored by the hIOmon software.

• No computer system restart is required in order to complete the hIOmon software installation and configuration.

A "hIOmon Disk I/O Ranger" icon is placed upon the desktop along with the “Start -> Programs -> hIOmon -> hIOmon Disk I/O Ranger” shortcut (both of which are added by the Windows Installer as part of the hIOmon software installation process).

A " temporary licensing period" is established starting from the date upon which the WIOP software is installed.  A "hIOmon Activation Key" must be activated during this period so that the WIOP software can be used for the full time period purchased by the associated subscription fee.  See the "Activate" button for additional information.

NOTE that the following section pertains only to the hIOmon "Workload I/O Profiler Files (WIOPF)":

Like the WIOP, the WIOPF software is provided within a software installation package file, either the "hIOmonInstall32.exe" file (for 32-but operating systems) or the "hIOmonInstall64.exe" file (for 64-bit operating system).  Simply run the software installation package, which will invoke the standard Windows Installer that will perform the actual installation of the hIOmon software.  Administrator privileges are required to perform the installation process, which typically takes just a few minutes to complete.

Please note that during this installation process, you will need to:

• Agree to the hyperI/O LLC "End-User Software License Agreement (EUSLA)"

• Enter the specific "serial number" that you received from hyperI/O LLC for installing the hIOmon software

• Specify whether the automated configuration script is to be run as part of the installation process.  The configuration options and actions performed by this script are the same as those provided by the automated configuration script within the WIOP.

• No computer system restart is required in order to complete the hIOmon software installation and configuration.

A "hIOmon Disk I/O Ranger" icon is placed upon the desktop along with the “Start -> Programs -> hIOmon -> hIOmon Disk I/O Ranger” shortcut (both of which are added by the Windows Installer as part of the hIOmon software installation process).

A " temporary licensing period" is established starting from the date upon which the WIOPF software is installed.  A "hIOmon Activation Key" must be activated during this period so that the WIOPF software can be used for the full time period purchased by the associated subscription fee.  See the "Activate" button for additional information.

A "hIOmon Disk I/O Ranger" icon is placed upon the desktop along with the “Start -> Programs -> hIOmon -> hIOmon Disk I/O Ranger” shortcut (both of which are added by the Windows Installer as part of the hIOmon software installation process).

NOTE that the following section pertains only to the "On-the-Web (OTW)" version of the hIOmon Disk I/O Ranger Display software:

The "On-the-Web (OTW)" version runs within a supported Web Browser:

• Internet Explorer version 11

• Microsoft Edge

• Firefox version 62 or above

• Chrome version 64 or above

• Safari version 11 or above

Configuration Information

NOTE that the following section pertains only to the hIOmon "Workload I/O Profiler (WIOP)":

The hIOmon ETW I/O Monitor software must be properly configured in order to collect the "Performance Threshold Range Metrics" for real-time display by the hIOmon Disk I/O Ranger Display.  This proper configuration includes an active/loaded hIOmon "Filter Selection" (see the "Filter Selection" description below) along with enabling the collection and processing of the I/O operation performance metrics.

A default automated configuration script (named "hIOmonCfgWIOP.vbs") creates a Filter Selection during the installation of the WIOP software.  This default Filter Selection specifies that the operating system physical disk associated with the system drive (typically the C: logical drive) is to be monitored by the hIOmon software.  A customized installation option is provided during the WIOP software installation process that allows you to also specify one or more Logical Disks whose associated physical disks are to be monitored.  See the "WIOP Installation" information above.

In addition, this automated configuration script activates/loads the created Filter Selection.  It then automatically enables the collection of the I/O operation performance metrics, including their summarization.

Please note that the "summary" metrics collected by hIOmon are summarized I/O operation performance metrics which are automatically aggregated by the hIOmon ETW I/O Monitor at the time that it observes the individual I/O operations as based upon the respective Microsoft ETW I/O operation trace data. 

A "Settings" button/option is located at the bottom of the "hIOmon Disk I/O Ranger Display" window.  Clicking on this button will cause the "Settings" popup window to be displayed.  The "Settings" window includes a "Reconfigure" button, which can be clicked to re-run the automated configuration script; as noted above, this script enables you to specify additional (or other) physical devices to be monitored by the hIOmon ETW I/O Monitor.

NOTE that no computer system restart is required to complete the activation of the configuration changes made by the automated configuration script.

The "Settings" window also allows you to select a specific hIOmon Manager Export File or ETW input log file whose I/O operation performance metrics are to be retrieved and shown within the hIOmon Disk I/O Ranger Display window (i.e., instead of the real-time metrics display).

Options are additionally provided that allow you to start and stop the retrieval of metrics from the selected hIOmon Manager Export File. 

NOTE that the following section pertains only to the hIOmon "Workload I/O Profiler Files (WIOPF)":

The hIOmon ETW I/O Monitor software must be properly configured in order to collect the "Performance Threshold Range Metrics" for display by the hIOmon Disk I/O Ranger Display.  This proper configuration includes an active/loaded hIOmon "Filter Selection" along with enabling the collection and processing of the I/O operation performance metrics.

The hIOmon "Filter Selection" specifies the particular devices/files that are to be monitored by the hIOmon I/O Monitor as well as the specific types of I/O operations to be monitored and the types of I/O operation performance metrics to be collected.  Moreover, the collection of I/O operation performance metrics generally begins when the Filter Selection is loaded/activated (these metrics are also reset to zeros when a Filter Selection is re-loaded/activated).

More specifically, the active Filter Selection must be configured to request the monitoring of read I/O operations (if "Read Range Counts" are to be displayed) and/or write I/O operations (if "Write Range Counts" as to be displayed) along with the collection of "summary" metrics (including "Device Summary" metrics)  for the particular devices and/or files of interest.

The default automated configuration script used by the WIOP software can be run during the installation of the WIOPF software.  A separate automated configuration script (named "hIOmonCfgWIOPiot.vbs") is also included within the hIOmon WIOPF software package.  This additional script can be used to configure the hIOmon WIOPF software so that it also collects device I/O operation trace records that are exported to a hIOmon Manager Export File.  See the WIOPF "Reconfigure" button option for how to run this script after the hIOmon WIOPF software has been installed.

NOTE that no computer system restart is required to complete the activation of the configuration changes made by the automated configuration script. 

Please note that the "summary" metrics collected by hIOmon are summarized I/O operation performance metrics which are automatically aggregated by the hIOmon ETW I/O Monitor at the time that it observes the individual I/O operations as based upon the respective Microsoft ETW I/O operation trace data.

The hIOmon "Disk I/O Ranger Display" provides a simple and quick way to display a selected subset (specifically the "Performance Threshold Range Metrics") within the large, comprehensive set of summary metrics that can be captured, displayed, and exported by hIOmon.

Please note that the WIOPF also provides configuration options that enable you to manually add, modify, and activate Filter Selections (including the ability to specify particular files that are to be monitored).  These WIOPF configuration options are in addition to the automated configuration script support that is included within the WIOP.  Additional information can be found within the "Getting Started" section below. 

NOTE that the following section pertains only to the "On-the-Web (OTW)" version of the hIOmon Disk I/O Ranger Display software:

Click on the "Settings" button/option located at the bottom of the "hIOmon Disk I/O Ranger" display window.  This will cause the "Settings" popup window to be displayed.

The "Settings" window allows you to select what is to be shown within the hIOmon DIOR Display window.

Options are also provided that allow you to start and stop the retrieval of I/O operation performance metrics from the selected source.  In addition, there are a number of other control options that, for example, enable you to select which particular I/O operation performance metrics are to be displayed.

Please note that web browser cookies must be enabled in order to save various display configuration options between successive "sessions" of the Disk I/O Ranger Display OTW.

Getting Started

NOTE that the following section pertains only to the hIOmon "Workload I/O Profiler (WIOP)":

To use/run the hIOmon Disk I/O Ranger Display, simply double-click upon the "hIOmon Disk I/O Ranger" desktop icon or use the “Start -> Programs -> hIOmon -> hIOmon Disk I/O Ranger” shortcut.

As noted within the "Configuration Information" section above, an automated configuration script is run during the installation of the WIOP software.  This script configures the hIOmon I/O Monitor software to monitor the operating system physical disk associated with the system drive (typically the C: logical drive).  A customized installation option is provided during the WIOP software installation process that allows you to also specify one (or more) other Logical Disks whose associated physical disks are to be monitored (i.e., leave the "Monitor only the System Drive and the associated physical volume/device" checkbox unchecked).

In addition, the script automatically configures the hIOmon software so that three distinct types of hIOmon Manager Export Files are created and activated.  These export files are configured to contain a comprehensive set of summarized I/O operation performance metrics for the individual physical devices and individual processes that are monitored.  These summary metrics go far beyond simple I/O operation counts and data transferred amounts and include the hIOmon "Performance Threshold Range Metrics", random and sequential access metrics, and much more.  In addition, these hIOmon Manager Export Files can subsequently be used as the input source of metrics for display by the hIOmon "Disk I/O Ranger Display".

One type of hIOmon Manager Export File will contain the summary I/O metrics for the physical disks being monitored.  A separate type will contain a variety of "Data Transfer Size (DTS)" summary metrics for the physical disks being monitored; these DTS metrics reflect I/O operation activity observed by the hIOmon I/O Monitor for I/O operations whose data transfer size/length was that of the corresponding size/length.  The third type will contain summary I/O metrics for each individual process instance that has its respective I/O operations performed by the physical disks being monitored.

Please note that these summary I/O operation performance metrics are collected upon a cumulative basis and are offloaded/written to the export files upon a ten-minute periodic basis.  The hIOmon Manager Export Files are configured so that the maximum allowed size for an individual export file is four mebibytes (i.e., roughly 4 megabytes).  A separate new hIOmon Manager Export File of the same type will automatically be created when this maximum size is reached for an export file.

Also note that the "Settings" window display "Reconfigure" button can be used to modify the hIOmon "Filter Selection" (so as to alter which particular devices are to be monitored) and that the use of this button does not modify any of the existing hIOmon Manager Export Files. 

NOTE that the following section pertains only to the hIOmon "Workload I/O Profiler Files (WIOPF)":

To use/run the hIOmon Disk I/O Ranger Display, simply double-click upon the "hIOmon Disk I/O Ranger" desktop icon or use the the “Start -> Programs -> hIOmon -> hIOmon Disk I/O Ranger” shortcut.

When first run after the installation of the hIOmon WIOPF software package, the hIOmon Disk I/O Ranger Display application will by default determine whether there is an existing Filter Selection that is currently active.  An active Filter Selection will be found if you selected the default automated configuration script to be run during the installation of the WIOPF software.

If no active Filter Selection is found, then the hIOmon Disk I/O Ranger Display application will automatically perform the following steps:

1. Create a Filter Selection (named "IORangerFS" by default) that will include a single filter specifying that both read and write I/O operations for all files upon the system drive (typically the "C:" logical disk) are to be monitored by the hIOmon I/O Monitor and that "summary" I/O operation performance metrics are to be collected for the monitored files.

2. In addition, "Device Summary" metrics will also be collected for the system drive; these "Device Summary" metrics reflect the combined totals for all of the monitored files that reside upon the system drive logical disk and for which the hIOmon I/O Monitor observed read and/or write I/O operations.

3. Will display an input prompt asking whether you also want both read and write I/O operations to be monitored by the hIOmon I/O Monitor for the operating system physical disk associated with the system drive logical disk.  If you enter a response indicating "Yes", then an additional filter for this physical disk will be included within the created Filter Selection; this filter will specify that "summary" I/O operation performance metrics are to be collected by the hIOmon I/O Monitor for both read and write I/O operations to the physical disk.

   If the associated physical disk is to be monitored, then an additional input prompt will be displayed asking whether you also want to collect "Data Transfer Size (DTS)" metrics for the physical disk.  Note that these DTS metrics will be collected upon a "device summary" basis for the physical disk.

4. After successfully creating this "IORangerFS" Filter Selection, the hIOmon Disk I/O Ranger Display application will then load/activate this Filter Selection and then activate the collection of the requested I/O operation performance metrics within the hIOmon I/O Monitor.  The hIOmon I/O Monitor will immediately begin monitoring I/O operations for files residing upon the system drive logical disk and collecting summary metrics.

   Please note that no reboot of the system will be required.

5. The hIOmon Disk I/O Ranger Display application will then make the "IORangerFS" Filter Selection the "default" Filter Selection.  The hIOmon Manager software component loads the "default" Filter Selection (if any) automatically each time the system is started.

The hIOmon Disk I/O Ranger Display application is initially configured so that only the combined "Read/Write" IOPS and ResponseTime (RT) metrics are displayed, with the display refreshed with the current metric values upon a five-second periodic basis.  This initial configuration does not include the optional collection of the DTS (Data Transfer Size) summary metrics.

Please note that the above configuration settings for the hIOmon Disk I/O Ranger Display application can be changed by using the "Settings" button/option at the bottom of the "Main Display".

NOTE that the following section pertains only to the "On-the-Web (OTW)" version of the hIOmon Disk I/O Ranger Display software:

The On-The-Web version of the hIOmon Disk I/O Ranger software can be accessed at the web site made available by the hIOmon REST API web service.

This web site is identified by the particular remote computer name, domain name, or IP address followed by the specific port associated with the hIOmon REST API web service.

The specific URL for the hIOmon Disk I/O Ranger OTW includes "/hIOmonOnTheWeb/hIOmonDiskIORanger/hIOmonDiskIORangerOTW.html"; for example (where "xxx.xxx.xx.xx" is the IP address and "pppp" is the port number):

http://xxx.xxx.xx.xx:pppp/hIOmonOnTheWeb/hIOmonDiskIORanger/hIOmonDiskIORangerOTW.html

The hIOmon DIOR Display OTW can be accessed using either HTTP or HTTPS.  See the "Remote Computer Setting" help information for how to specify a web site address (i.e., a remote computer) using the hIOmon REST API and HTTPS.

A "Session Sign-In" pop-up window will immediately then be shown upon access.  Your "session" (i.e., your use of the hIOmon DIOR Display OTW) will begin after you have successfully performed the "session sign-in".  The "Settings" button and the "Trender Display" button located at the bottom of the "hIOmon Disk I/O Ranger" display window will both be enabled once you have successfully signed-in.  Click on the "Settings" button to select the particular monitored item and I/O operation performance metrics to be displayed.  Also see the "OTW Configuration Information" above.

A "Session Sign-Out" pop-up window will appear to notify you that your session has ended.  It will be displayed when you close the hIOmon DIOR Display OTW web browser window.

If you are using a Safari browser, please note that you must click on the "Close" button to perform a "Session Sign-Out" rather than simply closing the web browser window.  This "Close" button will be located to the right of the "Settings" and "Trender Display" buttons at the bottom of the main hIOmon Disk I/O Ranger Display.

Your web browser settings must be configured to allow Pop-Ups so that these session sign-in and sign-out pop-up windows can be displayed.  Typically pop-ups can be allowed by disabling the Pop-Up Blocker within the web browser.

The Session Sign-In display window will show you the number of days remaining within the hIOmon REST API subscription period along with the subscription ending date.  You can also click the "About" button upon the "Settings" display window to show the expiration date.

Main Display

The Main Display includes the optional detailed display of the basic "Performance Threshold Range Metric" groups (i.e., the IOPS, MBs, Queue Depth (QD), Response Time (RT), and Data Transfer Size (DTS) Range Counts) along with important contextual information:

• Monitored Item Name.  This is the name of the device, file, or process for which the selected Performance Threshold Range Metrics are being displayed in real-time.  The name is shown at the top of the Main Display in black text within a white background.  The name will be truncated with an appended "..." if the length of the name exceeds the width of the Main Display window (this can occur with some long file names).

The "Settings" button at the bottom of the Main Display can be used to select a different monitored item to be displayed.  Simply click on the "Settings" button, then select the item of interest from the drop-down list box of names near the top of the "Settings" window and click on the "OK" button at the bottom of the "Settings" window.  The hIOmon Disk I/O Ranger display window will change to display the summary I/O operation performance metrics for the selected item of interest; also note that the selected item will be highlighted with a green background within the drop-down list of names (since it is the item currently being shown within the hIOmon Disk I/O Ranger display).  See the "Metrics for monitored:" description below for additional details.

• Disk Capacity Info.  Disk capacity information is only available for monitored Devices (i.e., Logical Disks and Physical Drives).  The information shown is the device capacity in terms of the total number of addressable bytes (with the total converted to gigabytes and gigibytes also displayed within the parentheses).

Additionally shown is the total amount of used bytes of the device capacity.  For a physical disk, the total number of device bytes used is the combined total of the current used bytes of each Logical Disk/Drive that resides upon the associated physical drive (i.e., the Logical Disk capacity minus the amount of 'free space' available for the Logical Disk) and the size of each GPT partition such as the 'EFI System Partition' and the Recovery Partitions. Note that this value only applies to Logical Disks and Physical Drives.

The total amount of used bytes of the device capacity is also shown in terms of gigabytes and as a percentage of the total number of addressable bytes.

The last two percentages displayed are the minimum and maximum percentages of used bytes observed for the device.

• Observation Period.  This is the overall length of time during which the hIOmon I/O Monitor captured the displayed Performance Threshold Range and associated metrics.  Please note that the respective time duration converted into seconds is also displayed.  Also note that this Observation Period generally begins when the hIOmon I/O Monitor started monitoring the corresponding monitored item (i.e., the displayed file, device, or process); that is, when the first monitored I/O operation was observed by the hIOmon I/O Monitor for the respective file or process after the Filter Selection was loaded (or reloaded).  In the case of devices, the Observation Period begins when the Filter Selection is loaded (or reloaded).

An "Active Time" percentage is additionally displayed.  This value reflects the percentage of time during the Observation Period that I/O operations were active for the monitored item (i.e., issued I/O operations being processed, including those queued).

• Reads.  This provides the overall total number of Read I/O operations observed during the Observation Period for the respective file, device, or process.  The total amount of data transferred (both in bytes and converted to mebibytes) by these read I/O operations is also shown, followed by the read "random I/O operation percentage", the read "random data transferred percentage", and the hIOmon read "DataTransferred/Time Index" metric (which is highlighted in yellow text).

The read "Random I/O operation percentage" is calculated by dividing the number of random read I/O operations by the combined sum of random read and sequential read I/O operations.  An I/O operation is considered to be sequential if its starting data transfer address is contiguous to the ending data transfer address of the prior I/O operation; in the case of the "Read random I/O operation percentage", the prior read I/O operation applies.  Please also note that the first I/O operation to a file is considered to be neither a random nor a sequential I/O operation; this also applies to the first monitored I/O operation to a physical device.

The read "Random data transferred percentage" reflects the percentage of the data that was transferred by the random read I/O operations.  This percentage is calculated by dividing the amount of data transferred by the random read I/O operations by the combined sum of the data transferred by the random read and by the sequential read I/O operations.

The hIOmon read "DataTransferred/Time Index (DXTI)" metric is calculated by simply taking the observed overall total amount of data transferred by the read I/O operations (converted to megabytes for scaling), and then dividing this combined total amount by the corresponding combined sum of the observed time durations (i.e., response times) of the read I/O operations that were performed to transfer this data.  The resulting value is considered to be an index.

The basic idea behind the hIOmon "DataTransferred/Time Index" metric is straightforward and simple:  "Better" storage I/O operation performance is fundamentally about transferring (more) data faster.  So for a given amount of data, transferring this data more quickly (i.e., in less time).  And similarly, transferring more data within the same amount of time.  More specifically, the relationship is basically between the amount of data transferred and the corresponding amount of time that it took to perform the I/O operations required for the data transfer.

Overall, this Index metric provides a "high-level" means for relative comparison of I/O performance, where basically "higher is better"; that is, the "higher" the Index number, the better the performance - as in more data transferred and/or less required response time (i.e., application wait).  It resembles the "fuel economy" index for an automotive vehicle (i.e., "miles-per-gallon" or "kilometres/litre") as an overall measure of "performance efficiency".  It is akin to more miles driven (more data transferred) for fuel used (response time taken to transfer this data), or similarly, same miles (data transferred) but less fuel (less response time).

Lastly. please note that you can select (within the "Settings" option window) whether the IOPS, MBs, QD, RT, and/or DTS Range Counts (as described below) are to be shown within the "Main Display".  Note that at least one of the "Read Range Counts" display options must be selected for the Read metrics to appear; also if no read I/O operations have been observed by the hIOmon I/O Monitor, then nothing will be displayed for the "Read Range Counts".

• Response Times.  This provides the minimum, average, and maximum Read I/O operation response time observed by the hIOmon I/O Monitor during the Observation Period for the respective file, device, or process.

Also shown is the percentage of the total number of Read I/O operations whose response time was less than one millisecond.

• IOPS Range Counts.  Each IOP Range Count reflects the total number of times that the hIOmon I/O Monitor observed an I/O operations-per-second (IOPS) within the corresponding range for I/O operations that were successfully performed.  Only those IOP Range Counts that have a non-zero value are displayed.  The individual IOP Range Counts are defined as follows:
  

  IOPS 1 - 99:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the first "IOPS Range".  By default, the first IOPS Range is an IOPS of one or more, but less than 100 I/O operations.  Also note that all I/O operations included within the IOPS Range Counts reflect I/O operations that were successfully performed.

  IOPS 100 - 499:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the second "IOPS Range".  By default, the second IOPS Range is an IOPS of between 100 and 499 I/O operations inclusive.

  IOPS 500 - 999:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the third "IOPS Range".  By default, the third "IOPS Range" is an IOPS of between 500 and 999 I/O operations inclusive.

  IOPS 1000 - 1999:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the fourth "IOPS Range".  By default, the fourth "IOPS Range" is an IOPS of between 1000 and 1999 I/O operations inclusive.

  IOPS 2000 - 4999:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the fifth "IOPS Range".  By default, the fifth "IOPS Range" is an IOPS of between 2000 and 4999 I/O operations inclusive.

  IOPS 5000 - 9999:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the sixth "IOPS Range".  By default, the sixth "IOPS Range" is an IOPS of between 5000 and 9999 I/O operations inclusive.

  IOPS 10000 - 19999:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the seventh "IOPS Range".  By default, the seventh "IOPS Range" is an IOPS of between 10000 and 19999 I/O operations inclusive.

  IOPS 20000 - 39999:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the eighth "IOPS Range".  By default, the eighth "IOPS Range" is an IOPS of between 20000 and 39999 I/O operations inclusive.

  IOPS 40000 and >  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of completed Read I/O operations within the ninth "IOPS Range".  By default, the ninth "IOPS Range" is an IOPS of 40000 or more I/O operations inclusive.

  User-selected threshold range values for the IOPS Ranges can optionally be specified and used instead of the default range values noted above.  The hIOmon WMI support, the hIOmon Browser and hIOmon CLI included with the hIOmon Add-Ons, and the hIOmon REST API can be used to specify particular user-selected ranges within the hIOmon Filter Selection.

  Also note that for each IOPS Range Count value displayed, a percentage is also always shown following the overall value. This percentage is the IOPS Range Count value divided by the total number of seconds that comprise the Observation Period.  As such, it basically indicates the percentage of time within the Observation Period that the respective IOPS Range Count value (e.g., "IOPS 1 - 99") was observed by the hIOmon I/O Monitor.

  The second percentage is the running sum/total percentage of the IOPS Range Count values for the respective IOPS Range Count, starting with the first IOPS Range Count value.  This percentage reflects the percentage of the Observation Period time during which the observed Read I/O operations IOPS was within the respective IOPS range or below (e.g., for the third IOPS Range Count, the percentage of the Observation Period time during which the observed IOPS was 1999 or less read I/O operations per second).  And accordingly, the percentage shown for the last Read IOPS Range Count value displayed essentially reflects the percentage of the Observation Period time during which the hIOmon I/O Monitor observed read I/O operations.

  The maximum observed IOPS for Read I/O operations is also shown for the highest displayed IOPS Range Count.

  See the respective "display ops/data amounts" option to optionally display extended information for the IOP Range Counts.

• MBs Range Counts.  Each MBs Range Count reflects the total number of times that the hIOmon I/O Monitor observed an actual megabytes-per-second (MB/s) transfer amount within the corresponding range for I/O operations that were successfully performed.  Only those MBs Range Counts that have a non-zero value are displayed.  The individual MBs Range Counts are defined as follows:
  

  MBs < 1:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the first "Megabytes Per Second (MBs) Range".  By default, the first "MBs Range" is a MB/s of less than one MB/s.  Also note that all I/O operations included within the MBs Range Counts reflect I/O operations that were successfully performed.

  MBs 1 < 10:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the second "MBs Range".  By default, the second "MBs Range" is a MB/s of between 1 and above but less than 10 MB/s.

  MBs 10 < 20:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the third "MBs Range".  By default, the third "MBs Range" is a MB/s of between 10 and above but less than 20 MB/s.

  MBs 20 < 50:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the fourth "MBs Range".  By default, the fourth "MBs Range" is a MB/s of between 20 and above but less than 50 MB/s.

  MBs 50 < 100:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the fifth "MBs Range".  By default, the fifth "MBs Range" is a MB/s of between 50 and above but less than 100 MB/s.

  MBs 100 < 200:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the sixth "MBs Range".  By default, the sixth "MBs Range" is a MB/s of between 100 and above but less than 200 MB/s.

  MBs 200 < 500:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the seventh "MBs Range".  By default, the seventh "MBs Range" is a MB/s of between 200 and above but less than 500 MB/s.

  MBs 500 < 1000:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the eighth "MBs Range".  By default, the eighth "MBs Range" is a MB/s of between 500 and above but less than 1000 MB/s.

  MBs 1000 and >:  The accumulated count of one-second time intervals during which the hIOmon I/O Monitor observed an actual total number of data bytes transferred by Read I/O operations within the ninth "MBs Range".  By default, the ninth "MBs Range" is a MB/s of 1000 or more.

  User-selected threshold range values for the "MBs Ranges" can optionally be specified and used instead of the default range values noted above.  The hIOmon WMI support, the hIOmon Browser and hIOmon CLI included with the hIOmon Add-Ons, and the hIOmon REST API can be used to specify particular user-selected ranges within the hIOmon Filter Selection.

  Also note that for each MBs Range Count value displayed, a percentage is also always shown following the overall value. This percentage is the MBs Range Count value divided by the total number of seconds that comprise the Observation Period.  As such, it basically indicates the percentage of time within the Observation Period that the respective MBs Range Count value (e.g., "MBs < 1") was observed by the hIOmon I/O Monitor.

  The second percentage is the running sum/total percentage of the MBs Range Count values for the respective MBs Range Count, starting with the first MBs Range Count value.  This percentage reflects the percentage of the Observation Period time during which the observed megabytes-per-second (MBS) transfer amount was within the respective MBs range or below (e.g., for the third MBs Range Count, the percentage of the Observation Period time during which the observed MB/s was less than 20 MB/s).

  The maximum observed megabytes-per-second for Read I/O operations is also shown for the highest displayed MBs Range Count.

  See the respective "display ops/data amounts" option to optionally display extended information for the MBs Range Counts.

• Queue Depth (QD) Range Counts.  Each QD Range Count reflects the total number of times that the hIOmon I/O Monitor observed an actual Queue Depth/Length within the corresponding range.  Only those QD Range Counts that have a non-zero value are displayed.  The individual QD Range Counts are defined as follows:
  

  QD > 1:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operations Queue Depth/Length greater than one; that is, where two or more Read I/O operations were concurrently outstanding (had not yet completed and includes requests in service).

  QD = 2:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the first "QD Range".  By default, the first QD Range Count is a queue depth of two (2).

  QD = 3:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the second "QD Range".  By default, the second QD Range Count is a queue depth of three (3).

  QD = 4:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the third "QD Range".  By default, the third QD Range Count is a queue depth of four (4).

  QD 5 - 7:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the fourth "QD Range".  By default, the fourth QD Range Count is a queue depth of between 5 and 7 inclusive.

  QD 8 - 15:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the fifth "QD Range".  By default, the fifth QD Range Count is a queue depth of between 8 and 15 inclusive.

  QD 16 - 31:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the sixth "QD Range".  By default, the sixth QD Count Range is a queue depth of between 16 and 31 inclusive.

  QD 32 - 63:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the seventh "QD Range".  By default, the seventh QD Count Range is a queue depth of between 32 and 63 inclusive.

  QD 64 and >:  The accumulated number of times that the hIOmon I/O Monitor observed a Read I/O operation queue depth within the eighth "QD Range".  By default, the eighth QD Count Range is a queue depth of 64 or more.

  User-selected threshold range values for the "QD Ranges" can optionally be specified and used instead of the default range values noted above.  The hIOmon WMI support, the hIOmon Browser and hIOmon CLI included with the hIOmon Add-Ons, and the hIOmon REST API can be used to specify particular user-selected ranges within the hIOmon Filter Selection.

  Also note that for the first QD Range Count only (i.e., "QD > 1"), a percentage is shown following the overall value.  This percentage is the QD Range Count value divided by the overall total number of Read I/O operations observed during the Observation Period.  As such, it basically indicates the percentage of Read I/O operations that experienced a Queue Depth of more than one Read I/O operation as observed by the hIOmon I/O Monitor.

  Separate percentages are also shown for the other Queue Depth ranges.  Two percentages are shown for each of these QD Ranges.  The first percentage is the respective QD Range Count value divided by the overall total number of Read I/O operations.  The second percentage is the percentage of the running sum/total of the QD Range Count values for the respective QD Range Count.

  The maximum observed Queue Depth for Read I/O operations is also shown for the highest displayed QD Range.

• Response Time (RT) Range Counts.  Each RT Range Count reflects the total number of times that the hIOmon I/O Monitor observed an I/O operation whose response time (i.e., the time duration between the start of an I/O operation and the completion of the I/O operation, which includes both the service time and the queue time) was within the corresponding range.  Please note that only those I/O operations that were successfully performed are included within the RT Range Counts and only those RT Range Counts that have a non-zero value are displayed.  The individual RT Range Counts are defined as follows:
  

  RT < 50us:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the first "Response Time (RT) Range".  By default, the first RT Range Count is a response time of less than 50 microseconds.

  RT 50us < 100us:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the second "Response Time (RT) Range".  By default, the second RT Range Count is a response time of 50 microseconds or more but less than 100 microseconds.

RT 100us < 200us:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the third "Response Time (RT) Range".  By default, the third RT Range Count is a response time of 100 microseconds or more but less than 200 microseconds.

RT 200us < 500us:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the fourth "Response Time (RT) Range".  By default, the fourth RT Range Count is a response time of 200 microseconds or more but less than 500 microseconds.

RT 500us < 1ms:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the fifth "Response Time (RT) Range".  By default, the fifth RT Range Count is a response time of 500 microseconds or more but less than 1 millisecond.

RT 1ms < 5ms:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the sixth "Response Time (RT) Range".  By default, the sixth RT Range Count is a response time of 1 millisecond or more but less than 5 milliseconds.

RT 5ms < 10ms:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the seventh "Response Time (RT) Range".  By default, the seventh RT Range Count is a response time of 5 milliseconds or more but less than 10 milliseconds.

RT 10ms < 100ms:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the eighth "Response Time (RT) Range".  By default, the eighth RT Range Count is a response time of 10 milliseconds or more but less than 100 milliseconds.

RT 100ms < 500ms:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the ninth "Response Time (RT) Range".  By default, the ninth RT Range Count is a response time of 100 milliseconds or more but less than 500 milliseconds.

RT 500ms and >:  The accumulated count of Read I/O operations whose time duration (response time) as observed by the hIOmon I/O Monitor was within the tenth "Response Time (RT) Range".  By default, the tenth RT Range Count is a response time of 500 milliseconds or more.

User-selected threshold range values for the "RT Ranges" can optionally be specified and used instead of the default range values noted above.  The hIOmon WMI support, the hIOmon Browser and hIOmon CLI included with the hIOmon Add-Ons, and the hIOmon REST API can be used to specify particular user-selected ranges within the hIOmon Filter Selection.

Also note that for each RT Range Count value displayed, two percentages are also always shown following the overall value.  The first percentage is the respective RT Range Count value divided by the combined sum of the RT Range Count values.  As such, it basically indicates the percentage of applicable Read I/O operations that experienced the respective Response Time ranges as observed by the hIOmon I/O Monitor.

The second percentage is the percentage of the running sum/total of the RT Range Count values for the respective RT Range Count, starting with the first RT Range Count value.  This percentage reflects the percentage of Read I/O operations that experienced a response time within the respective Response Time range or below (e.g., for the fourth RT Range Count, the percentage of the total number of Read I/O operations whose response time was less than 500 microseconds).

See the respective "display ops/data amounts" option to optionally display extended information for the RT Range Counts.

• Data Transfer Size (DTS) Range Counts.  Each DTS Range Count reflects the total number of times that the hIOmon I/O Monitor observed an I/O operation whose data transfer size/length was that of the corresponding size/length.  Please note that only those I/O operations that were successfully performed are included within the DTS Range Counts and only those DTS Range Counts that have a non-zero value are displayed.

  The DTS summary I/O operation performance metrics are not included within the base set of summary I/O operation performance metrics that are collected for an individual file, device, or process.  Rather, the separate collection of the DTS summary metrics must be explicitly enabled within the Filter Selection for the particular file, device, and/or process of interest.

  When the collection of DTS summary metrics is enabled, the hIOmon I/O Monitor will always by default collect DTS summary metrics for a fixed, basic set of data transfer sizes; this set starts with 512 bytes and successively doubles the size up to 8 MiB; that is, 512 bytes, 1024 bytes (1 KiB), 2048 bytes (2 KiB), 4096 bytes (4 KiB), etc. up to and including 8 MiB.

  Up to ten (10) additional user-specified data transfer sizes can optionally be specified within the Filter Selection.  These ten user-specified data transfer sizes apply globally to all monitored files, devices, and processes indicated by the Filter Selection.  For example, if a user-specified data transfer size of 12288 bytes was specified, then the 12288 byte data transfer size would apply to all files, devices, and processes for which DTS summary metrics are being collected.

  One of these 10 user-specified data transfer sizes can be a "wildcard", which indicates that the hIOmon I/O Monitor is to also include within the DTS summary metrics any data transfer size observed for the individual file/device (apart from the default, fixed set and any additional data transfer size already explicitly included within the user-specified set of data transfer sizes) up to an overall total of ten user-specified data transfer sizes (either explicitly or implicitly by use of the wildcard).  For example, if the Filter Selection has a single user-specified data transfer size that was explicitly specified (e.g., 12 KiB) along with the "wildcard", then the next nine data transfer sizes observed (apart from the fixed set and the 12 KiB data transfer sizes) will implicitly be included within the user-specified set of 10 additional data transfer sizes for the individual file, device, and/or process DTS summary metrics being collected.

  Please note that the option to configure the user-specified data transfer sizes within a Filter Selection is not supported by the hIOmon Disk I/O Ranger Display application; however, other hIOmon clients (e.g., the hIOmon WMI Browser, the hIOmon CLI, the hIOmon REST API, etc.) do provide the ability to configure the Filter Selection user-specified data transfer sizes.

  The default, fixed set of individual DTS Range Counts are defined as follows:
  

  DTS 512:  The accumulated count of Read I/O operations whose data transfer size/length was 512 bytes.

  DTS 1 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 1024 bytes.

DTS 2 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 2048 bytes.

DTS 4 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 4096 bytes.

DTS 8 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 8192 bytes.

DTS 16 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 16384 bytes.

DTS 32 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 32768 bytes.

DTS 64 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 65536 bytes.

DTS 128 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 131 072 bytes.

DTS 256 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 262 144 bytes.

DTS 512 KiB:  The accumulated count of Read I/O operations whose data transfer size/length was 524 288 bytes.

DTS 1 MiB:  The accumulated count of Read I/O operations whose data transfer size/length was 1 048 576 bytes.

DTS 2 MiB:  The accumulated count of Read I/O operations whose data transfer size/length was 2 097 152 bytes.

DTS 4 MiB:  The accumulated count of Read I/O operations whose data transfer size/length was 4 194 304 bytes.

DTS 8 MiB:  The accumulated count of Read I/O operations whose data transfer size/length was 8 388 608 bytes.

Any additional, user-specified data transfer sizes for which DTS summary metrics have been collected are displayed with a "DTS+" followed by the data transfer size.  For example, if a user-specified data transfer size of 12288 bytes was observed, the respective DTS Range Count metrics would be displayed with "DTS+ 12 KiB".  Similarly, if a user-specified data transfer size of 1536 bytes was observed, then the respective DTS Range Count metrics would be displayed with "DTS+ 1536".

Also note that for each DTS Range Count value displayed, a percentage is also always shown following the overall value.  This percentage is the respective DTS Range Count value divided by the total number of successful read I/O operations.  As such, it basically indicates the percentage of applicable Read I/O operations that used the respective data transfer size as observed by the hIOmon I/O Monitor.

If the collection of DTS summary metrics is not enabled for the specific file, device, or process, then nothing will be shown for the file, device, or process within the DTS Range Counts portion of the hIOmon Disk I/O Ranger Display.

The hIOmon DTS summary metrics support also includes corresponding DTS summary metrics for an associated physical device I/O operation for which hIOmon "Physical Device Extended" summary metrics are being collected.  For instance, if a data transfer size of 4 KiB was observed by the hIOmon I/O Monitor for a physical device I/O operation (for which "Physical Device Extended" summary metrics are being collected), then a separate set of DTS summary metrics would be collected and maintained for this "PhyDev" 4 KiB data transfer size apart from the DTS 4 KiB summary metrics collected/maintained for the associated file I/O operation.  These "PhyDev"-related DTS summary metrics are not shown by the hIOmon Disk I/O Ranger Display application; however, they can be displayed by the other hIOmon clients (e.g., the hIOmon WMI Browser, the hIOmon CLI, and the hIOmon REST API).

• Writes.  This provides the overall total number of Write I/O operations observed during the Observation Period for the respective file, device, or process.  The total amount of data transferred (both in bytes and converted to mebibytes) by these write I/O operations is also shown, followed by the write "random I/O operation percentage", the write "random data transferred percentage", and the hIOmon write "DataTransferred/Time Index" metric (which is highlighted in yellow text).

Please note that at least one of the "Write Range Counts" display options (as shown upon the "Settings" display window) must be selected for the Write metrics to appear; also if no write I/O operations have been observed by the hIOmon I/O Monitor, then nothing will be displayed for the "Write Range Counts".

As with the Read I/O operations, you can select (within the "Settings" display window) whether the IOPS, MBs, QD, RT, and/or DTS Range Counts (as described above, but for write I/O operations only) are to be displayed.

• Reads/Writes.  This provides the overall total number of combined Read and Write I/O operations observed during the Observation Period for the respective file, device, or process along with the corresponding read and write percentages of this combined total.  The total amount of data transferred (both in bytes and converted to mebibytes) by these combined read and write I/O operations is also shown, followed by the corresponding read and write percentages of this combined total, then followed by the read/write "random I/O operation percentage", the read/write "random data transferred percentage", and the hIOmon read/write "DataTransferred/Time Index" metric (which is highlighted in yellow text).

In the case of the read/write "random" percentages, the prior I/O operation can be either a read or a write I/O operation.  The hIOmon read/write "DataTransferred/Time Index" metric is calculated by taking the observed overall  total amount of data transferred by the read and write I/O operations combined (converted to megabytes for scaling), and then dividing this combined total amount by the corresponding combined sum of the observed time durations (i.e., response times) of the read and write I/O operations that were performed to transfer this data.

Please note that at least one of the "Read/Write Range Counts" display options (as shown upon the "Settings" display window) must be selected for the combined Read/Write metrics to appear; also if no read nor write I/O operations have been observed by the hIOmon I/O Monitor, then nothing will be displayed for the "Read/Write Range Counts".

As with the Read I/O operations, you can select (within the "Settings" display window) whether the IOPS, MBs, QD, RT, and/or DTS Range Counts (as described above, but for combined read and write I/O operations) are to be displayed.

Also please note the following:

1. All of the above metrics reflect the total, cumulative values that have been automatically accumulated by the hIOmon I/O Monitor during the indicated Observation Period.  Also please note that only those I/O operations that were successfully performed (i.e., transferred data) are included within the displayed IOPS, MBs, RT, and DTS Range Counts.  In addition, the DTS Range Counts require that the separate, optional collection of DTS summary metrics be enabled within the Filter Selection for the particular file, device, and/or process of interest.
   

2. Note that the first "one-second interval" begins with the first monitored read (in the case of the read and the combined read/write metrics) or write (in the case of the write and the combined read/write metrics) I/O operation observed by the hIOmon I/O Monitor for the respective file, device, or process.

3. The metrics are displayed upon a individual monitored item basis (i.e., for a single file, process, logical disk, or physical device).  The "Settings" button/option can be used to select a different monitored item for which the metrics are to be displayed.

4. The display of the metric values is periodically refreshed/updated automatically to the current values (real-time metrics) or the latest retrieved values (from a hIOmon Manager Export File).  You can view the refresh/retrieval time interval by clicking on the "Settings" button/option; the "Settings" options can also be used to select a different refresh/retrieval time interval.  Also please note that only those IOPS, MBs, QD, RT, and DTS Range Counts that have a non-zero value are displayed.
   

5. An error indication may be displayed near the bottom of the Main Display in the event that the hIOmon Disk I/O Ranger Display software encounters an error.  Click on the "Settings" option/button to view additional details about the error.
   

6. If a Filter Selection change is made while the installed version of the hIOmon Disk I/O Ranger Display software is active (i.e., is running), then the hIOmon Disk I/O Ranger Display will subsequently display the selected metrics for the new Observation Period.
   

7. You can invoke/run more than one instance of the installed hIOmon Disk I/O Ranger Display application.  Each instance can be configured to display the current metrics for a different monitored item (i.e., file, process, logical disk, or physical device).

Settings Display

The Settings Display includes the following display information and configuration options:

• Metrics for monitored:  Three monitored item types are shown: Devices, Files, and Processes.  When you select one of these three options, the drop-down list box immediately below will be populated with the respective items for which there are Performance Threshold Range Metrics currently available for display.

For example, if you click on the "Devices" button, the label of the drop-down list box will change to "Device names:" and the drop-down box will list the names of all devices for which Performance Threshold Range Metrics are available for display within the Main Display.  Similarly, if you click on the "Files" button, a list of file names (for files for which metrics are available for display) will be shown within the drop-down list box; a list of process names (for which metrics are available for display) will be shown within the drop-down box if the "Processes" button is selected.

To refresh the list of names within the drop-down list box, simply close and then re-open the "Settings" window.  The "Settings" window also refreshes the list of names within the drop-down list box each time that you select a different monitored item type option (so to force a refresh of the names within the drop-down list box, select a different monitored item type option and then reselect the monitored item type of interest).

To select a different monitored item to be displayed within the hIOmon Disk I/O Ranger display window, simply select the item of interest from the drop-down box list of names, then click on the "OK" button at the bottom of the "Settings" window.  Also note that selected item will be highlighted with a green background within the drop-down list of names (since it is the item currently being shown within the hIOmon Disk I/O Ranger display).

When a hIOmon Manager Export File is used as the source of the I/O operation performance metrics to be displayed, then these three display options (i.e., the Devices, Files, and Processes buttons) are appropriately limited/disabled to reflect the content of the selected hIOmon Manager Export File.  For example, if the hIOmon Manager Export File contains device I/O metrics, then the "Files" and "Processes" buttons are disabled (since the export file contains only device I/O metrics).

• Metrics from:  This drop-down list box is used to select the source of the summary I/O operation performance metrics to be displayed.  The box is populated with the hIOmon I/O Monitor types currently available from which the metrics can or could be retrieved.  When listed, the "hIOmon Manager Export File" source provides the option to retrieve metrics from a selected hIOmon Manager Export File rather than from a hIOmon ETW I/O Monitor type.

  Note that the "hIOmon Manager Export File" source, the ETW input log file source, and the ETW output log file options are not present/available in the demonstration version of the WIOP software since that version only supports the display of I/O metrics from the hIOmon ETW real-time I/O Monitor.

  When the "hIOmon Manager Export File" source or the ETW input log file source is selected, use the "Select file to retrieve from:" option below to select the particular hIOmon Manager Export File or ETW input log file respectively from which the I/O operation metrics are to be retrieved for display.

  Note the ETW input log files must include process, thread, and disk (including disk I/O initiation) event types.  Disk_File and file (including file I/O initiation) events types must additionally be included for monitoring file I/O operations.

  When the "ETW Realtime and Output File" or "ETW OutputFile Only" is selected, use the "Select output log file:" option below to select/specify the particular ETW output log file to which the ETW event trace data is to be written.

  Only one of the "ETWRealtime", "ETWRealtimeAndOutputFile", or "ETWOutputFileOnly" options can be loaded at a time; that is, if the "ETWRealtime" hIOmon ETW I/O Monitor is for example loaded, then neither the "ETWRealtimeAndOutputFile" nor the "ETWOutputFileOnly" ETW I/O Monitor can be loaded as well.

  The currently selected sources of metrics are highlighted with a green background within the drop-down list.

  NOTE that Display refreshes must first be stopped before changing the metrics retrieval source.

  The hIOmon ETW real-time I/O Monitor will continue to collect I/O operation metrics while the display refresh has been stopped or the display is actively showing metrics from another source (e.g., an ETW input log file).  Likewise, the separate hIOmon ETW I/O Monitor using an ETW input log file as the source of metrics will continue to retrieve ETW event information from the ETW log file while the display is stopped or showing metrics from another source (e.g., a hIOmon Manager Export File).

  Metrics from an "hIOmon Manager Export File" source can be displayed while the hIOmon ETW real-time I/O Monitor and/or hIOmon ETW input log file I/O Monitor continues to collect/retrieve its respective metrics.  However, the metrics from the hIOmon Manager Export File can no longer be displayed after a refresh of either the ETW real-time or ETW input log file metrics has been displayed.

• Device names (or File names or Process Names):.  This drop-down list box displays the full names of the monitored items for which there are Performance Threshold Range Metrics available for display.  This list of names can be either device, file, or process names depending upon which one of the three "Metrics for monitored:" buttons is currently selected.

  To display metrics for a particular monitored item (i.e., a specific device, file, or process), simply select the specific monitored item of interest and then click on the "OK" button.  Please note that the selection will immediately take effect upon clicking the "OK" button.  Please see the "OK" button below for additional details.

  The particular monitored item for which metrics are currently being displayed in the Main Display is highlighted with a green background within the drop-down list box.  Also please note that alongside each physical device name are the drive letters of the particular Logical Disks that are associated with the respective physical device.

  Lastly, please note that the specified physical device represents a physical device at the respective level within the Windows operating system.  The "physical device", for instance, is akin to the Windows Performance Monitor "PhysicalDisk" performance object (with "\Device\Harddisk0\DR0", as an example, representing physical device 0).

• Sort Order.   This drop-down list box provides a list of the various sort-order options available.  The monitored items shown within the list of monitored items will be displayed in accordance with the particular sort-order options enabled.  For example, if the "Max IOPS Read" sort order is enabled in "Descending" order, then the device, file, and process names will be displayed in descending maximum read I/O operation IOPS order, with the device, file, and process with the highest number of observed read I/O operations per second appearing at the top of the list of respective names.

  To enable a sort order, first select the sort order within the drop-down list box.  Next enable either the "Ascending" or the "Descending" checkbox as desired.  Then click on the "Select" button.  The enabled sort order will then be displayed with a gray background within the drop-down list of available sort orders.

  Click on the "Refresh" button to refresh the list of device, file, or process names based upon the (newly) enabled sort order(s).

  To disable a sort order, first select the sort order within the drop-down list box.  Next clear both the "Ascending" and the "Descending" checkboxes.  Then click on the "Select" button. 

  Please note that more than one sort order option can be enabled.

• Seconds between refreshes.  This input text field enables you to specify the time interval between refreshes/updates/retrieval of the metrics displayed within the Main Display.  This time interval is specified in terms of seconds and must be a number greater than zero.

  The new refresh interval will immediately take effect upon clicking the "OK" button.  Please see the "OK" button for additional details.

  You can also temporarily stop the refresh update of the Main Display by clicking upon the "Stop" button located to the right of the input text field where the refresh time interval value is specified.  The "Stop" button is automatically changed to a "Start" button when the refresh update of the Main Display has been stopped.  Click on the "Start" button to resume the refresh update of the Main Display; note that an immediate refresh of the Main Display is performed when the "Start" button is clicked (and the subsequent refresh updates are performed in accordance with the specified refresh time interval).

  Note that stopping the refresh update of the Main Display for real-time metrics does not stop of the collection of I/O operation performance metrics by the realtime hIOmon ETW I/O Monitor (i.e., the "ETW Realtime" metrics source).  Similarly for hIOmon ETW Monitor log files (i.e., the "ETW Input File" metrics source), the hIOmon ETW I/O Monitor continues to retrieve I/O operation trace data from the ETW input log file even when the refresh update of the Main Display has been stopped.  You can switch between both of these hIOmon ETW I/O Monitor types when they are concurrently running.

  When retrieving I/O metrics from a hIOmon Manager Export File, note that stopping the refresh update of the Main Display stops the retrieval of the I/O operation performance metrics from the selected hIOmon Manager Export File.  You can resume the retrieval of metrics by clicking upon the "Start" button; the retrieval will resume with the next record within the export file (i.e., after the location within the file where the retrieval was stopped).  Click upon the "Restart" button to have the retrieval resume at the beginning of the export file.  Note that the contents of the hIOmon Manager Export File will no longer be available for display after you switch from this hIOmon Manager Export File to another metrics source.

• Read Range Counts.  This provides a separate checkbox for each of the four basic types of "Performance Threshold Range Metrics": IOPS, MBs, QD (Queue Depth), RT (Response Time), and Data Transfer Size (DTS).  To enable the display of Read I/O operation metrics for a particular type, simply enable/select the respective checkbox.

  For example, select/enable the "IOPS" checkbox to display the "IOPS Range Counts" for read I/O operations within the Main Display.  Please note that the "OK" button must subsequently be clicked for any changes to these checkboxes to take effect within the Main Display. 

• Write Range Counts.  This provides a separate checkbox for each of the four basic types of "Performance Threshold Range Metrics": IOPS, MBs, QD (Queue Depth), RT (Response Time), and Data Transfer Size (DTS).  To enable the display of Write I/O operation metrics for a particular type, simply enable/select the respective checkbox.  

  For example, select/enable the "MBs" checkbox to display the "MBs Range Counts" for write I/O operations within the Main Display.  Please note that the "OK" button must subsequently be clicked for any changes to these checkboxes to take effect within the Main Display. 

• Read/Write Range Counts.  This provides a separate checkbox for each of the four basic types of "Performance Threshold Range Metrics": IOPS, MBs, QD (Queue Depth), RT (Response Time), and Data Transfer Size (DTS).  To enable the display of combined Read/Write I/O operation metrics for a particular type, simply enable/select the respective checkbox.

  For example, select/enable the "QD" checkbox to display the "QD Range Counts" for read and write I/O operations combined within the Main Display.  Please note that the "OK" button must subsequently be clicked for any changes to these checkboxes to take effect within the Main Display. 

• Display ops/data amounts.  Several additional extended display options are provided: 

  IOPS ops/xfer:  When this checkbox is selected/enabled, several additional values and percentages are displayed for the IOPS Range Counts.  A third value and associated percentage are displayed that show the total number of I/O operations associated with the respective IOPS Range Count value and its respective percentage of the total number of I/O operations of the respective type (note that this total number of I/O operations can include both successful and unsuccessful I/O operations).  A fourth percentage (and associated value, which reflects the total amount of data transferred by the I/O operations associated with the respective IOPS Range Count value) is also shown; this is the respective percentage of the total amount of data transferred by the total number of I/O operations of the respective type.

  Following these two values (i.e., the IOs and MiB) and their associated percentages is the average (mean) response time value for the respective IOP Range Count value.  Lastly, the DXTI value for the respective IOPS Range Count value is displayed.

  The first two percentages that are always shown for IOPS Range Counts are described above.

  MBs ops/xfer:  W:  When this checkbox is selected/enabled, a third value and associated percentage are displayed that show the total amount of data transferred associated with the respective MBs Range Count value and its respective percentage of the total amount of data transferred by the sum of the MBs Range Count values.  A fourth value and associated percentage are displayed that show the total number of I/O operations associated with the respective MBs Range Count value and its respective percentage of the total number of I/O operations of the respective type (note that this total number of I/O operations can include both successful and unsuccessful I/O operations).

  Following these two values (i.e., the MiB and IOs) and their associated percentages is the average (mean) response time value for the respective MBs Range Count value.  Lastly, the DXTI value for the respective MBs Range Count value is displayed.

  The first two percentages that are always shown for MBs Range Counts are described above.

  RT data transfer:  When this checkbox is selected/enabled, a third value and associated percentage are displayed that show the total amount of data transferred associated with the respective RT Range Count value and its respective percentage of the total amount of data transferred by the sum of the RT Range Count values.

  The percentage shown is the percentage of the running sum/total of the amount of data transferred by the RT Range Count values for the respective RT Range Count, starting with the first RT Range Count value.  This percentage reflects the percentage of the total amount of data transferred within the respective Response Time range or below (e.g., for the fourth RT Range Count, the percentage of the total amount of data transferred by I/O operations whose response time was less than 500 microseconds).

  Following these percentages is the average (mean) response time value for the respective RT Range Count value.  Lastly, the DXTI value for the respective RT Range Count value is displayed.

  The first two percentages that are always shown for RT Range Counts are described above.

  DTS additional metrics:  This checkbox along with the drop-down list box (located to the right of the checkbox) enables you to optionally display additional summary metrics for the DTS Range Counts.  The drop-down box lists the particular summary metric types that are available for display.  Only one of the metric types can be selected at a time; the currently-selected metric type is highlighted with a green background.  The checkbox must be enabled/checked for the selected metric type to be included within the DTS Range Counts display.  A metric type from the drop-down list box must be selected prior to enabling the checkbox (otherwise an error message will be displayed indicating that a metric type must be selected).  Clearing the checkbox will de-select any selected metric type.

  The specific metric types that can optionally be included with the DTS Range Counts display are:

• DataTransferred.   This option displays the total amount of data transferred using the respective data transfer size along with its percentage of the overall total amount of data transferred (that is, the combined sum for all I/O operations of the respective type, i.e., Read, Write, or combined Read/Write and all data transfer sizes).

• DXTI.  This option displays the "DataTransferred/Time Index (DXTI)" value for the respective data transfer size.  The DXTI metric value is calculated by simply taking the observed overall total amount of data transferred using the respective data transfer size (converted to megabytes for scaling), and then dividing this combined total amount by the corresponding combined sum of the observed time durations (i.e., response times) of the I/O operations that were performed to transfer this data.  The resulting value is considered to be an index.  See the description above for additional information about the DXTI.

• IOPS.  This option displays two additional metrics: the "average I/O operations per second (IOPS) rate" and the "maximum observed IOPS".  The "average IOPS rate" is calculated by dividing the total number of I/O operations of the respective type observed for the respective data transfer size by the overall elapsed time (i.e., the "Observation Period" duration as shown at the top of the hIOmon Disk I/O Ranger Display).  The "maximum IOPS" reflects the maximum number of I/O operations per second of the respective type as observed by the hIOmon I/O Monitor for the respective data transfer size.  This value is the actual number of I/O operations detected by the hIOmon I/O Monitor during a one-second interval since the start of the "Observation Period".

• MBs.  This option displays two additional metrics: the "average megabytes-per-second (MB/s) rate" and the "maximum observed MB/s".  The "average MB/s rate" is calculated by dividing the total amount of data transferred using the respective data transfer size by the overall elapsed time (i.e., the "Observation Period" duration as shown at the top of the hIOmon Disk I/O Ranger Display).  The "maximum MBs" reflects the maximum amount of data transferred per second for the respective data transfer size.  This value is the actual total amount of data transferred (in megabytes) as observed by the hIOmon I/O Monitor during a one-second interval since the start of the "Observation Period".

• QueueDepth.  This option displays three additional metrics: the "QD > 1 count" and associated percentage for the respective data transfer size along with a maximum queue depth (QD) value.  The first additional metric shown reflects the accumulated number of times that the hIOmon I/O Monitor observed an I/O operations Queue Depth/Length greater than one; that is, where two or more I/O operations (regardless of read or write, and regardless of the respective data transfer size used) were concurrently outstanding (had not yet completed and includes requests in service) when an I/O operation of the respective type using this data transfer size was observed by the hIOmon I/O Monitor to have started.  Note that this count includes the I/O operation observed by the hIOmon I/O Monitor to have started. The associated percentage shown is this accumulated count divided by the total number of I/O operations of the respective type that used the respective data transfer size.
  
  The third additional metric shown reflects the maximum number of I/O Operations (regardless of read or write, and regardless of the respective data transfer size used) that were concurrently outstanding (had not yet completed and includes requests in service) when an I/O operation of the respective type using this data transfer size was observed by the hIOmon I/O Monitor to have started.  Note that this count includes the I/O operation observed to have started.

• RandomAccess.  This option displays the total number of random access I/O operations that used a data transfer size corresponding to the respective data transfer size along with its respective percentage of the total number of I/O operations of the respective type, followed by the percentage of these random access I/O operations whose response time was less than one millisecond as observed by the hIOmon I/O Monitor.  An I/O operation is considered to be random if its starting data transfer address is not contiguous to the ending data transfer address of the prior I/O operation.  In the case of the "Read random I/O operation percentage", the prior read I/O operation using any data transfer size applies; in the case of the "Write random I/O operation percentage", the prior write I/O operation using any data transfer size applies.  In the case of the "Read/Write random I/O operation percentage", either a prior read or write I/O operation using any data transfer size applies.

• ResponseTimes.  This option displays the minimum, average, and maximum response times actually observed by the hIOmon I/O Monitor for I/O operations of the respective type that used the respective data transfer size.  The average response time is calculated by dividing the cumulative response times of all I/O operations of the respective type by the total count of I/O operations observed for the respective type.  This option also displays the percentage of the I/O operations of the respective type that used the respective data transfer size and whose response time was less than one millisecond as observed by the hIOmon I/O Monitor.

• SequentialAccess.  This option displays the total number of sequential access I/O operations that used a data transfer size corresponding to the respective data transfer size along with its respective percentage of the total number of I/O operations of the respective type, followed by the percentage of these sequential access I/O operations whose response time was less than one millisecond as observed by the hIOmon I/O Monitor.  An I/O operation is considered to be sequential if its starting data transfer address is contiguous to the ending data transfer address of the prior I/O operation.  In the case of the "Read sequential I/O operation percentage", the prior read I/O operation using any data transfer size applies; in the case of the "Write sequential I/O operation percentage", the prior write I/O operation using any data transfer size applies.  In the case of the "Read/Write sequential I/O operation percentage", either a prior read or write I/O operation using any data transfer size applies.

• SuccessiveUse.  This option displays the accumulated number of times that the hIOmon I/O Monitor observed an I/O operation of the respective type using this data transfer size for which the prior I/O operation of the same type used the same data transfer size.  The associated percentage shown is this accumulated count divided by the total number of I/O operations of the respective type that used the respective data transfer size.

Note that the first percentage that is always shown for DTS Range Counts is described above.

Please note that the "OK" button must subsequently be clicked for any changes to these checkboxes to take effect within the Main Display.

• Change monitored devices:  WIOP only.  Click the "Reconfigure" button to re-run the default automated configuration script that is used as part of the hIOmon WIOP software installation process.  Re-running this script enables you to specify additional (or other) devices to be monitored by the realtime hIOmon ETW I/O Monitor.  Note that re-running the script will also reset the summary metrics to zeroes as a result of activating/loading the Filter Selection.

  For an "ETW Input File" metrics source, click the "Configure" button to run the default automated configuration script that is used as part of the hIOmon WIOP software installation process.  This script must be run after loading a new hIOmon ETW I/O Monitor for the selected ETW Input Log file.  Running this script will configure the new hIOmon ETW I/O Monitor in accordance with the script options; this configuration process will include loading the hIOmon Filter Selection into the hIOmon ETW I/O Monitor and immediately starting the retrieval from the ETW Input Log File.  Note that the "Retrieval Delay Options" can be used to effectively control the rate by which the hIOmon ETW I/O Monitor retrieves I/O operation trace data from an ETW input log file.

  For an "ETW Output File Only" type of hIOmon ETW I/O Monitor, the "Configure" button must be clicked after loading the hIOmon ETW I/O Monitor based upon the selected ETW Output Log file.  Running this script will configure the new hIOmon ETW I/O Monitor in accordance with the script options; this configuration process will include loading the hIOmon Filter Selection into the hIOmon ETW I/O Monitor and immediately starting the writing of ETW event trace data to the ETW Output Log File.

  After clicking the "Reconfigure" or "Configure" button and making any Filter Selection changes, click the "Metrics for monitored:" radio buttons to populate the monitored-items dropdown list boxes.  Select a monitored-item to be displayed, then click the "OK" button to refresh the main display with metrics for the selected monitored item.

  Note that the use of these buttons can modify the hIOmon "Filter Selection", which indicates the particular devices that are to be monitored.  Its use will not modify any of the existing hIOmon Manager Export Files.

  Also note that an automated configuration script different from the default automated configuration script can also be optionally used.  The drop-down list box located to the right of the "Reconfigure" button contains the file names of automated configuration scripts available to be used for reconfiguration.  Select the script file name from the box, then click the Reconfigure button.  The selected script name will be highlighted with a green background within the drop-down list box. 

  When connected to a hIOmon REST API web server, the drop-down list box contains the file name of the hIOmon "Configuration Parameter Files" that reside upon the respective hIOmon REST API web server.  Select a desired Configuration Parameter File from the drop-down list box, then click on the "Reconfigure" button to configure the hIOmon software upon the respective computer in accordance with the configuration parameters within the selected Configuration Parameter file.  An input text box will appear if Permission Code is required to perform the configuration request; enter the proper Permission Code within this text box before clicking upon the "Reconfigure" button.  See the hIOmon REST API documentation for additional details.

• Monitor devices using WIOP:  WIOPF only.  Click the "Reconfigure" button to run the WIOP default automated configuration script, which can optionally be run as part of the hIOmon WIOPF software installation process.  Running this script enables you to specify additional (or other) devices to be monitored by the hIOmon I/O Monitor software component in accordance with hIOmon software configuration settings used by the WIOP.  Running this script will also automatically create and activate hIOmon Manager Export Files in accordance with the WIOP configuration settings if these export files do not already exist.  Note that re-running the script will reset the summary metrics to zeroes as a result of activating/loading the Filter Selection.

  For an "ETW Input File" metrics source, the "Configure" button must be clicked after loading a new hIOmon ETW I/O Monitor for a selected ETW Input Log file.  Running this script will configure the new hIOmon ETW I/O Monitor in accordance with the script options; this configuration process will include loading the hIOmon Filter Selection into the hIOmon ETW I/O Monitor and immediately starting the retrieval from the ETW Input Log File.  Note that the "Retrieval Delay Options" can be used to effectively control the rate by which the hIOmon ETW I/O Monitor retrieves I/O operation trace data from an ETW input log file.

  For an "ETW Output File Only" type of hIOmon ETW I/O Monitor, the "Configure" button must be clicked after loading the hIOmon ETW I/O Monitor based upon the selected ETW Output Log file.  Running this script will configure the new hIOmon ETW I/O Monitor in accordance with the script options; this configuration process will include loading the hIOmon Filter Selection into the hIOmon ETW I/O Monitor and immediately starting the writing of ETW event trace data to the ETW Output Log File.

  After clicking the "Reconfigure" or "Configure" button and making any Filter Selection changes, click the "Metrics for monitored:" radio buttons to populate the monitored-items dropdown list boxes.  Select a monitored-item to be displayed, then click the "OK" button to refresh the main display with metrics for the selected monitored item.

  Note that the use of these buttons can modify the hIOmon "Filter Selection", which indicates the particular devices that are to be monitored.

  Also note that an automated configuration script different from the default automated configuration script can also be optionally used.  The drop-down list box located to the right of the "Reconfigure" button contains the file names of automated configuration scripts available to be used for reconfiguration.  Select the script file name from the box, then click the Reconfigure button.  The selected script name will be highlighted with a green background within the drop-down list box. 

  Note that an automated configuration script file named "hIOmonCfgWIOPiot" is included within the drop-down list box.  This script configures the WIOPF software to additionally collect device I/O operation trace records that are saved to a hIOmon Manager Export File.

  When connected to a hIOmon REST API web server, the drop-down list box contains the file name of the hIOmon "Configuration Parameter Files" that reside upon the respective hIOmon REST API web server.  Select a desired Configuration Parameter File from the drop-down list box, then click on the "Reconfigure" button to configure the hIOmon software upon the respective computer in accordance with the configuration parameters within the selected Configuration Parameter file.  An input text box will appear if Permission Code is required to perform the configuration request; enter the proper Permission Code within this text box before clicking upon the "Reconfigure" button.  See the hIOmon REST API documentation for additional details.

• Remote Computer:  WIOP/WIOPF Workstation/Server Versions, the hIOmon User-Interface (UI) AddOn, or the hIOmon Disk I/O Ranger Display "On-The-Web (OTW)" version.  The "Remote Computer" checkbox enables you to select whether the hIOmon Manager upon the local computer or instead upon a remote computer is to be the source of the metrics to be displayed. The "local" computer is the computer upon which the hIOmon Disk I/O Ranger Display software has been installed.

  Unless the "REST API" option is used, the remote computer is accessed using the hIOmon WMI support and requires that the Microsoft remote WMI access support also be enabled upon both the local and the remote computers.  This includes enabling the necessary WMI security and firewall permissions upon the remote computer.

  If the "Use REST API" checkbox is checked, then the remote computer is accessed using HTTP requests in accordance with the "hIOmon REST API" web service.  Note in this case the "hIOmon REST API" software support must be installed upon the targeted remote computer with the hIOmon REST API web service running.

  The remote computer can be identified by specifying either the computer name or IP address.  A user name and associated user password must also be specified when accessed using the hIOmon WMI support.

  If the hIOmon REST API is used, the remote computer name (or IP address) can be followed by a specific port (e.g., xxx.xxx.x.x:9000).  The default port will be used if a specific port is not appended to the remote computer name or IP address.

  In addition, the remote computer name or IP address must be prefixed by "SSL:" if the HTTPS support is enabled within the targeted hIOmon REST API web service (i.e., "SSL:xxx.xxx.xx.xx:ppppp").

  The installed application version of the hIOmon Disk I/O Ranger will display a prompt asking whether you want to connect to the specified remote computer.  It will also provide you an option to save separately (within the hIOmon Disk I/O Ranger "hIOdiorDisplay.parms" configuration file) the remote computer name (and also the user name and user password when the WMI support is used) as defaults.  Please note that these values will be saved in clear text.  If a remote computer was being accessed when the hIOmon Disk I/O Ranger Display was closed, then the hIOmon Disk I/O Ranger Display when next started will attempt to reconnect to the remote computer using these saved default values.  Click on the "Clear" button to delete the saved default values from the configuration file.

  A hIOmon REST API web server can be configured by its web server administrator to require JSON Web Token (JWT) authorization.  If the JWT support is enabled, then the hIOmon Disk I/O Ranger Display must obtain and use a token with the hIOmon REST API support.  When connecting to a remote computer, the installed application version of the hIOmon Disk I/O Ranger will require that the parameters needed to obtain a token be entered using the "Settings" window.  These parameters include "user name", "email address", and "password", which are entered using a "|" as the parameter delimiter (i.e., user name|email address|password).  Note that a new token is required for each separate use of the hIOmon Disk I/O Ranger Display.

  The hIOmon REST API web server administrator can configure the hIOmon REST API web service to require or make optional the token "password" parameter.  In addition, the hIOmon REST API web server can be configured to limit authorization tokens to only specific user names, email addresses, and passwords.

  The user name, email address, and access code entered during the OTW version session sign-in will automatically be used as the parameter values for obtaining the token.

  For the OTW version of the hIOmon Disk I/O Ranger, click on the "Change" button.  Enter the remote computer name or IP address and then click on the "Apply" button.  To save the entered remote computer name or IP address as the default value, first set/enable the associated "Save" checkbox prior to clicking upon the "Apply" button.  The saved default value will be subsequently used when starting the hIOmon Disk I/O Ranger Display.  Please note that the default value is saved using the web browser cookies, which must be enabled so that the default values can be saved.  Click on the "Clear" button to delete the saved values from the cookies file.

  Check the "Remote Computer" checkbox to indicate that the hIOmon Manager at the specified remote computer is to be accessed.  Clear the checkbox to indicate that the hIOmon Manager upon the local computer is to be accessed.  Then click on the "OK" button to complete the checkbox request.

  "REST API" will be displayed when the hIOmon REST API support is being used to communicate with the hIOmon Manager upon a remote computer.

• Monitored device/file.  WIOPF only. Either a drop-down list box (that lists all of the "filters" included within the currently selected "Filter Selection" and from which you can select a specific filter to be removed) or a text input box (that enables you to enter a new filter which is to be either added to the currently selected Filter Selection or to a new Filter Selection) is displayed.

  A hIOmon "Filter Selection" specifies the particular files/devices that are to be monitored by the hIOmon I/O Monitor.  The Filter Selection is comprised of one or more "filters", each of which identifies the specific name of a file or device that is to be monitored by hIOmon.

  Please note that those "filters" that are "exclusion" filters are identified with a gray background within the drop-down list box of filters that are present within the currently selected Filter Selection.  An "exclusion" filter is a filter whose file path name represents those files/directories that are explicitly excluded from being monitored by the hIOmon I/O Monitor (i.e., the hIOmon I/O Monitor will not collect any I/O operation performance metrics for those files/directories that have been explicitly excluded from being monitored by the hIOmon I/O Monitor). 

  Add:  To add a new filter to an existing Filter Selection, first select the specific Filter Selection to which you want to add the new filter.  The currently selected Filter Selection is highlighted within the "Filter Selections:" drop-down list box as described below.

  Then click on the "Add" button, after which a text input box will be displayed (instead of the drop-down box that shows all of the filters currently included within the selected Filter Selection).  Enter into this text box the filter that is to be added to the currently selected Filter Selection, then click upon the "Add" button again.  The hIOmon Disk I/O Ranger Display will then immediately update the Filter Selection by adding the filter specified within the text input box.  The drop-down list box of filters will then be shown with the newly added filter.

  To add the first filter to a Filter Selection being newly created, first click on the "Add" button, after which a text input box will be displayed (instead of the drop-down box listing the filters currently included within the selected Filter Selection).  Enter into this text box the filter that is to be included within the new Filter Selection to be created, then click upon the "New" button (rather than the "Add" button again).  The hIOmon Disk I/O Ranger Display will then immediately create a new Filter Selection that includes the filter specified within the text input box.  The drop-down list box of filters will then be shown that includes the filter, and the new Filter Selection will become the currently selected Filter Selection.     

  When specifying the filter, you can enter, for example, the following to monitor all files upon Logical Drive "C:":  C:\*  (or simply enter the letter C, in which case the hIOmon Disk I/O Ranger Display will automatically append the ":\*" wildcard indicator to the drive letter).

  To monitor a specific file, enter the full file path name; for instance: C:\pagefile.sys

  To monitor all files within a particular folder/directory, enter the full path name for the folder/directory followed by the wildcard indicator; for example: C:\Program Files\*

  To monitor a specific physical device, enter the full device name (e.g., \Device\Harddisk0\DR0) or simply enter the letter of a Logical Drive associated with the physical device along with the physical device alias character (an exclamation mark: "!"); for example: C!

  You can also simply enter the physical device number; for example, to monitor physical device \Device\Harddisk0\DR0, simply enter: DR0

  Remove:  To remove a filter from a Filter Selection, first select (from within the "Filter Selections:" drop-down list box) the specific Filter Selection from which you want to remove the filter.

  Then select the particular filter that you want to be removed from the drop-down list box that lists all of the "filters" included within the currently selected "Filter Selection".  After you have selected the particular filter to be removed, click on the "Remove" button.

  The hIOmon Disk I/O Ranger Display will then immediately update the selected Filter Selection by removing the filter that you selected.  Also note that the Filter Selection will automatically be deleted if the last filter within the Filter Selection is removed. 

  DTS:  To enable or disable the collection of DTS summary metrics for a particular file or file path, first select (from within the "Filter Selections:" drop-down list box) the specific Filter Selection that contains the filter for the file or file path for which you want to enable or disable the collection of DTS summary metrics.

  Then select the particular filter for which you want to enable or disable the collection of DTS summary metrics.  Those filters for which the collection of DTS file summary metrics is enabled are highlighted with an almond background color.  Those filters for which the collection of DTS device summary metrics is enabled are highlighted with a Sandy Brown background color.  And those filters for which the collection of both device and file DTS summary metrics is enabled are highlighted with a Sienna background color.

  To disable the collection of DTS summary metrics for such a filter, select the particular filter from within the drop-down list box of filters and then click on the "DTS" button located to the right of the "Remove" button.  The collection of DTS summary metrics will then immediately be disabled and the background color will change to white.  To enable the collection of DTS summary metrics for a filter (whose background color is white, which indicates that the collection of DTS summary metrics is not enabled for the filter), select the particular filter from within the drop-down list box of filters and then click on the "DTS" button; the collection of DTS summary metrics will then immediately be enabled for the filter and its background color will change to almond.  The "DTS" button can be used to toggle between DTS summary metrics collection enabled and disabled for a particular filter.

  Please note that when the collection of DTS summary metrics is enabled (or disabled) for a filter that is included within the currently active/loaded Filter Selection, the Filter Selection must be reactivated/loaded in order for the DTS summary metrics enable/disable to take effect.

  Also note that:
  

  • When the collection of DTS summary metrics is enabled for a filter, the collection of DTS summary metrics is also concurrently enabled for the associated device (i.e., DTS summary metrics will also be collected for the device if summary I/O operation performance metrics are already being collected for the device).

  • The "DTS" button cannot be used to enable (or disable) the collection of DTS summary metrics for process summaries.  Consequently, no DTS summary metrics will be shown for processes (unless the collection of DTS summary metrics for the processes was previously enabled by using another hIOmon client (e.g., the hIOmon WMI Browser; see the paragraph below).

  • The collection of DTS summary metrics for a device is not disabled when the collection of DTS summary metrics for an associated file is disabled by using the "DTS" button.  DTS summary metrics can be collected (when enabled) for a device even when the collection of DTS summary metrics is disabled for all of its associated files.  Consequently, DTS summary metrics will continue to be displayed for the device (reflecting the data transfer sizes used by the monitored files associated with the device), but no DTS summary metrics will be displayed for those files for which the collection of DTS summary metrics has been disabled by the "DTS" button.

  The options to configure the user-specified data transfer sizes within a Filter Selection and to enable/disable the collection of DTS summary metrics for processes are not supported by the hIOmon Disk I/O Ranger Display; however, other hIOmon clients (e.g., the hIOmon WMI Browser and the hIOmon REST API) do provide the ability to configure the Filter Selection user-specified data transfer sizes and to enable/disable the collection of DTS summary metrics for specific processes.

  Please note again that the Add, Remove, or DTS request is performed immediately upon the selected Filter Selection when you click upon the respective button.

• Filter Selections:  WIOPF only.  This drop-down list box contains the names of all of the Filter Selections currently available.  The currently loaded/active Filter Selection is identified by its name in red text.   The currently selected Filter Selection is highlighted with a green background.  The Filter Selection that is the default Filter Selection is identified with a gray background; the hIOmon Manager software component loads the "default" Filter Selection (if any) automatically each time the system is started.  An almond background color is used for a Filter Selection that is both the default and currently selected Filter Selection.

  Load:  To load/activate a specific Filter Selection, first select the respective Filter Selection within the drop-down list box, then click on the "Load" button.  The selected Filter Selection will then be immediately activated.  Please note that all of the summary metrics will subsequently be reset to zeroes as a result of loading/activating the Filter Selection; in addition, a new Observation Period will begin.

  The list of names for those monitored items for which there are Performance Threshold Range Metrics available for display will also change as a result of loading/activating the Filter Selection.  That is, those monitored items whose metrics were collected for the prior activated Filter Selection will subsequently be removed from this list of names so that only those monitored items for which there are Performance Threshold Range Metrics available for display based upon the currently loaded Filter Selection will be included within the list.  Please see the "Metrics for monitored:" description above for how to refresh the list of names of monitored items for which there are Performance Threshold Range Metrics available for display.

  Delete:  To explicitly delete a specific Filter Selection, first select the respective Filter Selection within the drop-down list box, then click on the "Delete" button.  The selected Filter Selection will then be immediately deleted and removed from list of currently available/present Filter Selections shown within the drop-down list box.  Please note that new Filter Selections can be added by using the "New" button described below.

  Default:  To assign a specific Filter Selection as the "default" Filter Selection, first select the respective Filter Selection within the drop-down list box, then click on the "Default" button.  The selected Filter Selection will then be immediately assigned as the new "default" Filter Selection.

• New Filter Selection name:  WIOPF only. This text box enables you to enter the name of the new Filter Selection that is to be created.

  To create a new Filter Selection, first click on the "Add" button associated with the "Monitored device/file:" options, after which a text input box will be displayed (instead of the drop-down box listing the filters currently included within the selected Filter Selection).  Enter a "filter" (i.e., the specific name of a device or file) that is to be included within the Filter Selection to be created; see the "Add" button above for a description of valid filter names. 

  Then enter the name of the new Filter Selection within this "New Filter Selection name:" text input box, and then finally click on the "New" button.  The Filter Selection (that includes the specified filter and requests that both read and write I/O operations be monitored) will then be immediately created and added to the list of Filter Selections currently shown within the Filter Selections drop-down box.  In addition, this newly created Filter Selection will become the currently selected Filter Selection, and the drop-down list box of filters will appear for this Filter Selection (this drop-down list box will include the filter that you specified as part of creating the new Filter Selection). 

  You can subsequently add additional filters to this new Filter Selection by using the "Add" button described above.

  Please note that a new Filter Selection must subsequently be loaded/activated in order for monitoring to be performed in accordance with this new Filter Selection.  That is, until this new Filter Selection is loaded/activated, the monitoring of I/O operations by the hIOmon I/O Monitor will continue to be performed based upon the currently loaded/activated Filter Selection.
  

• Enter Activation Information:  WIOP and WIOPF, and hIOmon REST API, if applicable.  This input text field enables you to specify the e-mail address (of the customer registered at the hIOmon web site who purchased the hIOmon software license or Subscription Extension) and Order ID associated with this license or Subscription Extension, both of which are required to activate or extend a hIOmon software subscription.

  The entered e-mail address and Order ID number are transmitted via the Internet to the hIOmon web site, which then returns the proper "hIOmon Key" value.  The hIOmon Disk I/O Ranger Display then uses this hIOmon Key to activate (or extend) the hIOmon software subscription.  The temporary licensing period for the associated installed WIOP, WIOPF, or hIOmon REST API software will be removed when first activating the software subscription. 

  Enter the e-mail address and Order ID separated by the "|" delimiter (e.g., "JohnDoe@there.com|12345") into the text field, then click upon the "Activate" button to the right of the input text field.  A message will be displayed at the bottom of the Settings window display to report whether the activation was successful or not.

  To activate or extend the subscription for the hIOmon REST API web service software component (i.e., the connected hIOmon REST API web service), enter the appropriate e-mail address and Order ID into the input text box and check the "REST API" check box located to the right of the "Activate" button.  Then click the "Activate" button to the right of the input text field.

  A permission code may be required to successfully perform an activation of a hIOmon Key for a hIOmon REST API web service. If it is required, follow the Order ID with another "|" delimiter, follwed by the permission code.

  Note that this input text field is only visible after the "Activate" button at the bottom of the Settings display window has been clicked.

• Max Allowed File Count:  WIOP and WIOPF.  This input text field enables you to specify the maximum number of files for which the hIOmon I/O Monitor can concurrently maintain I/O operation performance metrics.  This configurable parameter basically lets you control the maximum number of files that the hIOmon I/O Monitor is allowed to concurrently monitor.

  Note that the hIOmon I/O Monitor will record a System Event Log entry in the event that the monitoring of an additional file (or directory) would exceed the maximum allowed by this configurable parameter.  An error message will also be displayed within the Settings Display if the hIOmon Disk I/O Ranger Display detects that the maximum allowed number has been reached. 

  The value entered for the new maximum allowed number of files to be monitored concurrently must be a number greater than zero.  Please note that the "OK" button must subsequently be clicked for this new value to take effect.

  Note that the new maximum value will be put into effect asynchronously by the hIOmon I/O Monitor such that it might take several minutes to actually take effect.

• Retrieval Delay Options:  Retrieval from an ETW input log file.  These options enable you to effectively control the rate by which the hIOmon ETW I/O Monitor retrieves I/O operation trace data from an ETW input log file.

  The "I/O operation count delay" option can be used to specify the number of I/O operations that have to be processed/received by the hIOmon ETW I/O Monitor before waiting to retrieve the next record of ETW event data from the ETW input log file.  The default value is zero.  Note that the length of this subsequent wait period is set by the associated "Retrieval time delay" option, which must also be set to a non-zero value if this option is set to a non-zero value.  That is, a non-zero value for this option is ignored if no associated time delay period is set.

  The "Retrieval time delay" option can be used to specify the number of milliseconds (if any) for which the hIOmon ETW I/O Monitor is to delay before retrieving the next record of ETW event data from the ETW input log file.  Note that a value of zero (the default) indicates that there should be no delay (i.e., wait) period.

  NOTE that values for these two options must be entered before clicking on the "Load" button to load a hIOmon ETW I/O Monitor using the selected ETW input log file.

• Starting date/time:   Retrieval from hIOmon Manager Export File or ETW input log file.  This text box enables you to enter a year or starting date/time value for the I/O operation metrics to be retrieved from the selected hIOmon Manager Export File.

  If there is no "Year" column metric within the selected hIOmon Manager Export File, then the Disk I/O Ranger Display will assume the current year when displaying any date values.  If a four-digit year value is entered within this text box, then the Disk I/O Ranger Display will use this explicit year value when displaying any date values.

  If a starting date (or date and time) value is entered into this text box, then the Disk I/O Ranger Display will ignore (i.e., not display) all entries within the hIOmon Manager Export File that precede the specified date/time.  For example, if the hIOmon Manager Export File contains I/O operation metrics starting from August 8, 2014 through August 15, 2014 and you enter "Aug 12 2014" into the text box, then the Disk I/O Ranger Display will not display the I/O metrics for August 8th nor the following days before August 12th.

  Large hIOmon Manager Export Files can contain a large number of distinct monitored items (i.e., distinct device, process, or file names).  This can be particularly true for Process summary hIOmon Manager Export Files since they can contain the various separate executions of the same application (with each separate execution having its own unique process name that includes the associated PID value).

  Large numbers of distinct monitored items increase memory consumption within the hIOmon Disk I/O Ranger Display.  The increased memory consumption can entail termination of the hIOmon DIOR Display application.  A configurable "Monitored Item Limit" value option is provided by the hIOmon DIOR Display to help mitigate this memory consumption issue.

  The hIOmon DIOR Display will issue an error message (shown upon the Settings Display) when it detects that the number of monitored items read from a hIOmon Manager Export File is about to exceed the default value of the "Monitored Item Limit".  The value of the "Monitored Item Limit" will also be displayed upon the Setting Display within an input text box.  You can enter a new different value within this text box.  Note that the new value will be saved within the hIOmon DIOR Display configurable settings and used upon subsequent invocations of the hIOmon Disk I/O Ranger Display.

• Retrieve metrics from file:  Retrieval from hIOmon Manager Export File or ETW input log file.  This text box displays the hIOmon Manager Export File or ETW input log file from which I/O operation performance metrics are to be retrieved.

  This text box is automatically updated with the full file path name of the hIOmon Manager Export File or ETW input log file chosen by means of the "Browse..." button.  Any text manually entered into this text box is ignored.

• Select file to retrieve from:  Retrieval from hIOmon Manager Export File or ETW input log file.  Click on the "Browse ..." button to select the particular hIOmon Manager Export File or ETW input log file whose I/O operation performance metrics are to be retrieved for display.

  WIOP/WIOPF Workstation/Server Versions or the hIOmon User-Interface (UI) AddOn.  The "List Remote" button is additionally displayed for these versions when connected to a remote computer using the hIOmon REST API.  Click on this button to display a drop-down list box that appears above upon the "Retrieve metrics from file:" line.  As indicated within this drop-down list box, select a hIOmon Manager Export File from the list.  By default, this list of hIOmon Manager Export Files reflects those present upon the remote computer within the "...\hIOmonGr\ExportFiles" folder where the hIOmon software is installed.  The hIOmon Disk I/O Ranger Display will retrieve from the remote computer (using the hIOmon REST API) the metrics contained within the selected hIOmon Manger Export File.

  In addition, a "Get Coalesced" checkbox is displayed.  The drop-down list box will contain the file name (and associated file extension) of the coalesced hIOmon Manager Export Files when this checkbox is checked/enabled and the "List Remote" button is then clicked.  This list of coalesced hIOmon Manager Export Files reflects those present within the "...\hIOmonGr\ExportFiles" folder where the hIOmon software is installed.

  To list the coalesced hIOmon Manager Export Files that reside within a different folder upon the remote computer, enter the full file path of the directory into the input text box located to the right of the "Get Coalesced" checkbox, then click the "List Remote" button.

  An "Enter Permission Code:" input text box will also be displayed if a permission code must be supplied in order to retrieve the contents of the hIOmon Manager Export File selected within the drop-down list box.  Enter the proper permission code within this text box before selecting the particular hIOmon Manager Export File whose contents are to be retrieved.

  WIOP and WIOPF.  A "Coalesce" button is additionally displayed when a hIOmon Manager Export File is chosen as the metrics retrieval source.  Click this button to aggregate the existing hIOmon Manager Export Files.  The export files will be coalesced in the following fashion:

  • All currently-existing "Device Summary", "DTS Device Summary", and "Process Summary" hIOmon Manager Export Files residing within the "hIOmonGr\ExportFiles" folder (located where the hIOmon WIOP or WIOPF software was installed) will be coalesced.
    

  • A "hIOmon\ExportFiles\Coalesced" folder will be created within your "My Documents" folder.  All of the resulting coalesced export files noted below will be saved/written to this folder.  Any already-existing coalesced export file within this folder will first be deleted prior to the start of the following coalescing process.
    

  • A "Devices_Daily" export file will be generated from the aggregation based upon a daily basis.  Similarly, a "DTSdevices_Daily" export file and a "Processes_Daily" export file will generated from the aggregation based upon a daily basis.
    

  • A "Devices_Totals" export file will be generated from the aggregation based upon an overall totals basis.  Similarly, a "DTSdevices_Totals" export file and a "Processes_Totals" export file will generated from the aggregation based upon an overall totals basis.
    

  • The "Processes_Totals" export file will contain a row for each process instance (i.e., each separate execution of an application will result in an individual process instance).  A separate "Processes_Totals_PIDless" export file will also be generated; this export file will reflect the combined total of all process instances for the same application.
    

  • An informational message will be shown at the bottom of the "Settings" window display to indicate the current progress in the coalescent process.  The coalescing process might take some time.  As a result, warning messages might be issued indicating that the Disk I/O Ranger Display appears stalled.  To continue coalescing, respond to these warning messages by allowing the script to continue.
    

  • The resulting coalesced export files can be used as a hIOmon Manager Export File input source for metrics display by the hIOmon Disk I/O Ranger Display.

A "Remote Coalesce" button is additionally displayed when connected to a remote computer using the hIOmon REST API.  Click on this button to display a drop-down list box that appears above upon the "Retrieve metrics from file:" line.  As indicated within this drop-down list box, select a particular file from the list of "coalesce parameters files".  These files contain parameters associated with the requested operations to be performed when coalescing the specified hIOmon Manager Export Files (e.g., whether these export files should be coalesced upon a daily, weekly, or monthly basis).  See the "hIOmonManagerExportFilesCoalesceWorkspaceParmFile" description within the hIOmon REST API documentation for specific details regarding the Coalesce Parameters File.

Selecting a Coalesce Parameters File from the drop-down list box will cause the hIOmon DIOR Display to issue a hIOmon REST API request to the associated computer to perform a coalesce operation based upon the selected Coalesce Parameters File.  Note that an "Enter Permission Code:" input text box will also be displayed if a permission code must be supplied in order to perform the remote coalesce operation.  Enter the proper permission code within this text box before selecting the particular Coalesce Parameters File.

A "Load" button is additionally displayed when an ETW Input Log File is chosen as the metrics retrieval source.  Click this button to load a hIOmon ETW I/O Monitor using the ETW input log file selected as the metrics retrieval source.

After loading the ETW input log file, click on the "Configure" button to configure the hIOmon ETW I/O Monitor.  See "Change monitored devices" or "Monitor devices using WIOP" for additional details.

• Enter ETW output log file:  ETW output log file.  Enter within the input text box the full path file name for the ETW output log file to which the ETW event data is to be written.  This is shown for both the "ETW Realtime with Output File" and the "ETW Output File Only" hIOmon ETW I/O Monitor types.  You can use the "Select ETW output log file" Browser button (described below) to pre-populate this text box.

• Select ETW output log file:  ETW output log file.  Click on the "Browse ..." button to select a particular ETW output log file to which the ETW event trace data is to be written.  The full path file name of the selected file will be copied to the "Enter output log file" input text box noted above.  This selection option is shown for both the "ETW Realtime with Output File" and the "ETW Output File Only" hIOmon ETW I/O Monitor types.

A "Load" button is additionally displayed when the ETW Output Log File File type of hIOmon ETW I/O Monitor is chosen.  Click this button to load a hIOmon ETW I/O Monitor in preparation for using the ETW output log file.

After loading the hIOmon ETW I/O Monitor based upon the ETW output log file only, click on the "Configure" button to configure this hIOmon ETW I/O Monitor.  See "Change monitored devices" or "Monitor devices using WIOP" for additional details.

• Export metrics to file:  WIOP and WIOPF.  This option enables you to export/save Performance Threshold Range Metrics to a file; the particular metrics that you select are written to the specified export file each time the "Main Display" is refreshed.

  The text input box enables you to enter the name of the export file to which the metrics will be written.  Simply enter the file name for the export file; the hIOmon Disk I/O Ranger Display will automatically append a file extension of ".csv" (for the "Comma-Separated-Values" format of the export file) and the file will reside within the same folder/directory from which the hIOmon Disk I/O Ranger Display was started.

  Select metrics to include:  Located to the right of the text box (that contains the file name of the export file) is a drop-down list box that shows the names of the various Performance Threshold Range Metric types that can be included within the export file.

  Select a particular Performance Threshold Range Metric to have it included within the export file; those specific Performance Threshold Range Metrics that are to be included within the export file are highlighted with a green background.

  The hIOmon Disk I/O Ranger Display determines that a specific Performance Threshold Range Metric is to be selected (i.e., included within the export file) or unselected (i.e., not included within export file) when there is a change of the selected item within the drop-down list box.

  For example, say that you first click upon the "Date" item within the drop-down list box (so consequently its background becomes green, which indicates that this item will be included within the metrics written to the export file).

  If you then click upon the "Reads" item within the drop-down box, then the background color of this item will change to green, again an indication that this particular item is to be included within the metrics written to the export file.  If you next click upon the "Reads" item again, nothing will change.  However, if you then click upon another item (i.e., other than the "Reads" selection item) with the drop-down list box, for instance, the "Read Xfer", then the "Read Xfer" item will become highlighted with a green background and the corresponding total amount of data (in bytes) transferred by the read I/O operations will also be included within the export file.

  Note that if you then go back and click upon an already selected item (e.g., the "Date" item), this selected item will consequently become "unselected" (i.e., it will not be included within the export file) and its background will return to white (rather than green).

  There are several special items within the drop-down list box:  hIOmon Manager Export File, hIOmon Manager Export File DTS, SelectALL, and SelectDisplayedRCtypes.

  The hIOmon Manager Export File item is present only if the "Retrieve from hIOmon Manager Export File" configuration option is available.  If this drop-down list box option is selected, then the various summary I/O operation performance metrics currently available for display by the hIOmon Disk I/O Ranger Display will be written to the export file within the "hIOmon Manager Export File" format.  The resulting hIOmon Manager Export File can subsequently be used as an input source file from which the Disk I/O Ranger Display can retrieve the I/O metrics for display.  Note that is this export file option is selected, then all of the remaining drop-down list box items will be ignored.

  The hIOmon Manager Export File DTS item is present only if the "Retrieve from hIOmon Manager Export File" configuration option is available.  If this drop-down list box option is selected, then the various "Data Transfer Size (DTS)" summary I/O operation performance metrics currently available for display by the hIOmon Disk I/O Ranger Display will be written to the export file within the "hIOmon Manager Export File" format.  The resulting hIOmon Manager Export File can subsequently be used as an input source file from which the Disk I/O Ranger Display can retrieve the DTS I/O operation metrics for display.  Note that is this export file option is selected, then all of the remaining drop-down list box items will be ignored.

  The SelectALL item allows you to select all of the Performance Threshold Range Metrics (i.e., all of the Performance Threshold Range Metrics within the drop-down list box) simultaneously.  Conversely, if the SelectALL item is clicked when it has been selected (i.e., it has a green background), then all of the Performance Threshold Range Metrics within the drop-down list box will immediately become "unselected" (will return to a white background) and so will not be included within the export file.

  The SelectDisplayedRCtypes item allows you to select (for inclusion within the export file) all of the Performance Threshold Range Metrics that are associated with the particular Range Count metrics which have been chosen to be shown with the Main Display.  For example, if the Read Range Counts IOPS and MBs checkboxes are checked for display within the Main Display, then clicking upon the "SelectDisplayedRCtypes" item will result in all of the respective Read IOPS and MBs Range Count metrics being selected for inclusion within the export file (and so will be highlighted with a green background).

  The "Date" selection item represents the current date/time when the metrics were written to the export file.

  The "Name" selection item represents the name of the file, device, or process to which the exported Performance Threshold Range Metrics pertain.

  The "Reads", "Writes", and "Reads/Writes" selection items represent the total number of read I/O operations, write I/O operations, and the combined read and write I/O operations respectively.

  Similarly, the "Read Xfer", "Write Xfer", and "Read/Write Xfer" selection items represent the associated total amount of data transferred (in bytes) by the read I/O operations, write I/O operations, and combined read and write I/O operations respectively.

  The remaining selection items correspond to the various Performance Threshold Range Metrics that can be displayed within the Main Display as described above.

  Also note that the selection items that have either an "IOP", "Xfer", and "RAN" appended to the Performance Threshold Range Metric name represent the extended display options as described above.

  For example, in the case of the "Read IOPS 100-499 IOP" selection item, the exported metric is the total number of Read I/O operations that were observed within the corresponding "Read IOPS 100-499" range.  Similarly the "Write MBs 1<10 Xfer" selection item, for instance, represents the export metric that reflects the actual total number of data bytes transferred by Write I/O operations that were observed within the corresponding "Write MBs 1<10" range.         

  Please note the following:
  
  

  • A selected Performance Threshold Range Metric will be written to the export file even when its value is zero (this is unlike the Main Display, which only displays non-zero Performance Threshold Range Metrics).
    
    

  • An export file must contain at least one of the Performance Threshold Range Metrics items shown within the drop-down box that lists those Performance Threshold Range Metrics which can be included within an export file. 
    
    

  • All of the Performance Threshold Range Metrics to be included within the export file must be selected before you start/activate the export file (i.e., enable writing to the export file).
    
    

  • The selection of Performance Threshold Range Metrics to be included within an export file cannot be changed after the export file has been started/activated.
    
    

  • You must first stop the export file (if it is currently started/active) and then delete the export file before you can then select a modified set of Performance Threshold Range Metrics to be included within the same export file (i.e., an existing export with the same file name).
    
    

  • The Performance Threshold Range Metrics selections are preserved (within the saved configuration settings) across subsequent runs of the hIOmon Disk I/O Ranger Display.  Moreover, if an export file is enabled/active at the time that you exit the hIOmon Disk I/O Ranger Display, then the same export file will automatically be started (with the same selection settings) by the hIOmon Disk I/O Ranger Display the next time you start the display.

  Start  The Start button allows you to enable/activate the exporting of the selected Performance Threshold Range Metrics to the specified export file.  Please note that only one export file can be active at the same time.

  The current values of the Performance Threshold Range Metrics that were selected to be included within the active export file will be written to the activated export file with each periodic refresh of the Main Display.  The selected Performance Threshold Range Metric items will be displayed in red text when the export file is enabled for exporting.   

  The "Start" button will change to the "Stop" button immediately after the specified export file has been successfully enabled for exporting.  Click on the "Stop" button to disable further exporting to the export file; the "Stop" button will change back to the "Start" button after exporting to the export file has been successfully disabled.  Exporting to the export file will continue to be stopped until the "Start" button is again clicked.

  The "Delete" button allows you to delete the specified export file (as indicated by the file name entered into the text box that contains the file name of the export file).  A currently started/activated export file must first be stopped before deleting the export file. 

• OK Button.  Click on the "OK" button to immediately activate the configuration changes described above (e.g., the "Device/File/Process Names" and "Seconds between refreshes" configuration options).  Please note that if you click on the "OK" button without making any configuration changes, then the "Settings" display window will simply close and the operation of the hIOmon Disk I/O Ranger Display will continue without any change.

  Also please note that the configuration changes are persistent.  That is, the configuration options will be saved so that they will automatically be used the next time that you start/invoke the hIOmon Disk I/O Ranger Display.

• Cancel Button.  Click on the "Cancel" button to close the "Settings" display without activating/saving any of the changes that you have made to the configuration option input fields; that is, any such entered changes that have not yet been performed will be ignored.

• Help Button.  Click on the "Help" button to display this help information html page.

• About Button.  Click on the "About" button to display information about the hIOmon Disk I/O Ranger software such as the associated "hIOmon Product ID" along with the installation and expiration dates.

  The hIOmon Product ID is generated as part of the hIOmon WIOP (or WIOPF) software installation process.

  The expiration date shown is the date upon which the hIOmon WIOP (or WIOPF) software will expire (that is, the date upon which the hIOmon Manager service will terminate execution and the use of the hIOmon WIOP or WIOPF software is no longer licensed/permitted).  See the "Extend License" button below for additional information.

• Activate Button.  WIOP, WIOPF, and hIOmon REST API, if applicable.  A message is displayed at the bottom of the "Settings" window display for several days prior to the expiration date of the hIOmon Manager software subscription.  This message indicates the number of days remaining before the expiration of the hIOmon Manager software subscription.  Note that the "Activate" button, which is located to the far right of the "About" button, is not available with the demonstration version of the hIOmon software.

  A temporary licensing period is established when the WIOP (or WIOPF or hIOmon REST API) software is installed.  This period is seven (7) days in length; it begins upon the date that the hIOmon software is installed.  The associated expiration date is the day following the last day of the temporary licensing period.  The hIOmon software will no longer be operable when the expiration date is reached.

  The requisite "hIOmon Activation Key" (or "hIOmon Extension Key" when extending a hIOmon software subscription) must be obtained from hyperI/O LLC and then activated during this temporary licensing period (i.e., before the temporary expiration date is reached) in order to enable the full time period purchased by the subscription fee.

  A "hIOmon Activation Key" is a specific software character-string value generated by hyperI/O LLC that is based upon the installation date of the hIOmon software package.  When activated, the proper hIOmon Activation Key will remove the temporary licensing period and advance the expiration date in accordance with the actual hIOmon software installation date and the time period purchased by the subscription fee (e.g., 30 days from the date when the hIOmon software was installed).

  The appropriate e-mail address (of the customer registered at the hIOmon web site who purchased the hIOmon software license) and Order ID must be provided to hyperI/O LLC when obtaining a hIOmon Key. These are required so that the proper key value can be generated.  Click on the "About" button to display the software installation date and current expiration date for the hIOmon Manager software subscription.

  To activate a hIOmon Key, first click on the "Activate" button.  This will result in the "Enter Activation Information" input text field being shown within the Settings window display.  See the "Enter Activation Information" input text field description above for further instructions.

  Note that the "Activate Button" can also be used to extend a hIOmon software subscription.  The extension of the subscription requires the appropriate e-mail address (of the customer registered at the hIOmon web site who purchased the Subscription Extension) and the Order ID of the Subscription Extension.  See the "Enter Activation Information" input text field description above for further instructions.

  In addition, the "Activate Button" can be used to activate or extend the hIOmon REST API web service software component (i.e., the connected hIOmon REST API web service).  See the "Enter Activation Information" input text field description above for further instructions.

  Please note that attempts to activate invalid hIOmon Keys can cause fatal hIOmon software errors.

• Error Information.  In the event of an error, the bottom portion of the "Settings" display window will provide detailed information about the error encountered by the hIOmon Disk I/O Ranger Display.  This error information will be displayed in red and will be cleared when the "Settings" display window is closed.  Please the the "Error Messages" section below for additional information about each of the error messages that can be displayed.

I/O Trender Display

A "Trender Display" button appears to the right of the "Settings" button upon the Main Display window of the hIOmon Disk I/O Ranger when the hIOmon "I/O Trender Display" feature has been enabled and the required Internet Explorer version 10.0 or higher is installed.

The hIOmon "I/O Trender Display" can be used to optionally display - within a graphical format - metrics that have been retrieved by the hIOmon Disk I/O Ranger.  The hIOmon "I/O Trender Display" runs in conjunction with the hIOmon "Disk I/O Ranger Display", which transfers to the I/O Trender Display various metrics that it has retrieved.  These metrics are then shown by the I/O Trender Display in accordance with the various configuration options that are provided by the I/O Trender Display.

The "I/O Trender Display" graphs/charts are shown within the bottom frame of the hIOmon Disk I/O Ranger "Main Display".

See the help information provided by the hIOmon "I/O Trender Display" for additional information about the hIOmon "I/O Trender Display".  This help information can be accessed by clicking upon the "Customize" button located at the top of the "I/O Trender Display" window; this will cause the Trender "Settings" display panel to be shown.  The "Help" button at the bottom of the Trender "Settings" display panel can be used to display the hIOmon "I/O Trender Display" help information.

Error Messages

The following error, warning, and informational messages can be displayed by the hIOmon Disk I/O Ranger Display:

• HRCMD100E.  The hIOmon Disk I/O Ranger Display application has detected that the hIOmon Manager service does not appear to be currently running (and so the hIOmon Disk I/O Ranger Display application cannot retrieve the Performance Threshold Range Metrics from the hIOmon Manager).  You can verify whether the hIOmon Manager is currently running by going to the Windows "Administrative Tools", selecting the "Services" option, and viewing the current status of the "hyperI/O hIOmon Manager" service.
  
  Please note that the standard hIOmon software installation process configures the hIOmon Manager service so that it is automatically started when the system is started.  Also note that the hIOmon Manager will stop running when it detects that the hIOmon software expiration date (if any) has been reached.
  
  

• HRCMD120E.  The hIOmon WMI Support is not accessible/available.  Please ensure that the hIOmon software installation process was successfully performed (please see section 5.2 within the hIOmon "readMe" document).  Also note that this error can occur if the hIOmon WMI Support is not installed or has been uninstalled (e.g., as part of the uninstall/removal of the hIOmon software) or if the hIOmon Manager service is not running or is not accessible.
  
  

• HRCMD150W.  Either no physical devices are currently being monitored by the hIOmon software, or there are no I/O metrics currently collected for any of the monitored devices.  Please see the "Configuration Information" section above for how to properly configure the hIOmon software so that the particular physical device(s) of interest to you are monitored by the hIOmon software.
  
  

• HRCMD155W.  Either no files are currently being monitored by the hIOmon software, or there are no I/O metrics currently collected for any of the monitored files.  Please see the "Configuration Information" section above for how to properly configure the hIOmon software so that the particular files of interest to you are monitored by the hIOmon software.
  
  

• HRCMD158W.  Either no processes are currently being monitored by the hIOmon software, or there are no I/O metrics currently collected for any of the monitored processes.  Please see the "Configuration Information" section above for how to properly configure the hIOmon software so that the particular files and associated processes of interest to you are monitored by the hIOmon software.
  
  

• HRCMD200E.  No physical device is selected for which metrics are to be displayed.  Please select the particular physical device of interest within the "Device Names" drop-down box list.
  
  

• HRCMD205E.  No file is selected for which metrics are to be displayed.  Please select the particular physical device of interest within the "File Names" drop-down box list.
  
  

• HRCMD208E.  No process name is selected for which metrics are to be displayed.  Please select the particular physical device of interest within the "Process Names" drop-down box list.
  
  

• HRCMD250W.  No metrics were available for retrieval for the logical device or physical device identified within the error message.  This can occur if the active Filter Selection was changed during the refresh interval, with the change resulting in a Filter Selection that does not meet the configuration requirements described above.  Similarly, this error message will be shown if you try to display I/O operation performance metrics for a physical device, but the computer system has not yet be restarted in order for the hIOmon software configuration to complete.

  This can also occur if the summary I/O operation performance metrics for the monitored item have been offloaded to the hIOmon Manager service and there has been no subsequent monitored I/O operation activity to the monitored item.  Please note that in this case, summary I/O operation performance metrics will again be available for display upon the subsequent resumption of I/O operation activity to/by the monitored item.  
  
  

• HRCMD255W.  No metrics were available for retrieval for the file identified within the error message.  This can occur if the active Filter Selection was changed during the refresh interval, with the change resulting in a Filter Selection that does not meet the configuration requirements described above.  

  This can also occur if the summary I/O operation performance metrics for the monitored item have been offloaded to the hIOmon Manager service and there has been no subsequent monitored I/O operation activity to the monitored item.  Please note that in this case, summary I/O operation performance metrics will again be available for display upon the subsequent resumption of I/O operation activity to/by the monitored item.
  
  

• HRCMD258W.  No metrics were available for retrieval for the process name identified within the error message.  This can occur if the active Filter Selection was changed during the refresh interval, with the change resulting in a Filter Selection that does not meet the configuration requirements described above.  

  This can also occur if the summary I/O operation performance metrics for the monitored item have been offloaded to the hIOmon Manager service and there has been no subsequent monitored I/O operation activity to the monitored item.  Please note that in this case, summary I/O operation performance metrics will again be available for display upon the subsequent resumption of I/O operation activity to/by the monitored item.   
  
  

• HRCMD300E.  The hIOmon Disk I/O Ranger Display was not able to successfully update the metrics display due to the indicated error shown within the error message.
  
  

• HRCMD320E.  The hIOmon Disk I/O Ranger Display detected that the export file specified to be deleted was not found.
  
  

• HRCMD330E.  The hIOmon Disk I/O Ranger Display detected that the export file specified to be deleted is the export file that is currently enabled/activated for exporting; the currently enabled/activate export file must first be stopped before deleting the export file.
  
  

• HRCMD332I.  The hIOmon Disk I/O Ranger Display detected that the export file specified to be deleted could not be found; this can occur for an export file requested to be deleted that had been enabled/activated for exporting and stopped, but no export records had yet been written to the export file (so the export file itself does not exist yet).
  
  

• HRCMD335E.  The hIOmon Disk I/O Ranger Display encountered an error while trying to retrieve the file names of the hIOmon Manager Export Files located upon a remote computer using the hIOmon REST API support.
  
  

• HRCMD340I.  The end-of-file has been reached for the specified hIOmon Manager Export File.
  
  

• HRCMD342I.  The end of the ETW Input Log File has been reached and the input file has been closed.  The corresponding hIOmon ETW I/O Monitor remains accessible, but is stopped and must subsequently be unloaded.
  
  

• HRCMD343I.  The maximum number of rows to be retrieved from the hIOmon Manager Export File has been reached.
  
  

• HRCMD350E.  The hIOmon Disk I/O Ranger Display was not able to successfully retrieve the list of monitored items (i.e., device, file, or process names for which there are Performance Threshold Range Metrics available for display) due to the indicated error shown within the error message.
  
  If the Device Names box list shows "No monitored devices", then the currently active Filter Selection is not properly configured to monitor logical devices or physical devices.  If the Device Names box list shows "No monitored devices with metrics", then there are devices being monitored but no I/O metrics have been collected yet for any of these devices.  If the Device Names box list does show the devices, then the Filter Selection does not request that the required metrics (of the type indicated within the error message) be collected; consequently, the metrics cannot be retrieved/displayed by the hIOmon Disk I/O Ranger Display for the currently-selected device.
  
  Similarly, if the File Names box list shows "No monitored files with metrics", then the currently active Filter Selection is either not properly configured to monitor files or there are currently no files with collected I/O metrics.  If the File Names box list does show the files, then the Filter Selection does not request that the required metrics (of the type indicated within the error message) be collected; consequently, the metrics cannot be retrieved/displayed by the hIOmon Disk I/O Ranger Display for the currently-selected file.
  
  And if the Process Names box list shows "No monitored processes with metrics", then the currently active Filter Selection is either not properly configured to monitor any files associated with processes for which metrics are to be displayed or there are currently no processes with collected I/O metrics.  If the Process Names box list does show the process names, then the Filter Selection does not request that the required metrics (of the type indicated within the error message) be collected; consequently, the metrics cannot be retrieved/displayed by the hIOmon Disk I/O Ranger Display for the currently-selected process.
  
  Please see the "Configuration Information" section above for how to properly configure the hIOmon software so that the appropriate metrics are collected for display.
  
  

• HRCMD355E.  The hIOmon Disk I/O Ranger Display was not able to successfully retrieve the Data Transfer Size (DTS) summary I/O operation performance metrics from the hIOmon Manager for a monitored item (i.e., device, file, or process name for which there are Performance Threshold Range Metrics available for display) due to the indicated error shown within the error message.  Please see the "Configuration Information" section above for how to properly configure the hIOmon software so that the appropriate metrics are collected for display.
  
  

• HRCMD357E.  An excessive number of retries was encountered while attempting to invoke the hIOmon I/O Trender Display.
  
  

• HRCMD358E.  Internet Explorer version 10.0 (or later), which is required for the hIOmon I/O Trender Display, is not installed. Consequently, the hIOmon I/O Trender Display feature can not be used.
  
  

• HRCMD359I.  An attempt was made to open the hIOmon I/O Trender Display window when it was already open.
  
  

• HRCMD360E.  An invalid number was entered for the maximum allowed number of files that can be monitored concurrently by the hIOmon I/O Monitor.  Please enter a positive number, which represents the new maximum number of files for which the hIOmon I/O Monitor is allowed to concurrently maintain I/O operation performance metrics.
  
  

• HRCMD365I.  The maximum number of files for which the hIOmon I/O Monitor is allowed to concurrently maintain I/O operation performance metrics has been reached.  You can increase the maximum allowed number by using the Settings configuration option to do same.
  
  

• HRCMD376W.  Display refreshes must first be stopped before performing the configuration change.  Click the "Stop" button to suspend the display refreshes/retrieval.
  
  

• HRCMD379W.  Display refreshes must first be stopped before changing the metrics retrieval source (e.g., between the retrieval/display of the "real-time" I/O metrics and metrics retrieved from a hIOmon Manager Export File).  Click the "Stop" button to suspend the display refreshes/retrieval.
  
  

• HRCMD380E.  The hIOmon Disk I/O Ranger Display was not able to successfully retrieve the list of Filter Selection names currently present/extant due to the indicated error shown within the error message.
  
  

• HRCMD385E.  The hIOmon Disk I/O Ranger Display was not able to successfully retrieve the name of the Filter Selection that is currently assigned as the "default" Filter Selection due to the indicated error shown within the error message.
  
  

• HRCMD386E.  The hIOmon Disk I/O Ranger Display was not able to successfully retrieve the names of filters associated with the currently selected Filter Selection due to the indicated error shown within the error message.
  
  

• HRCMD387E.  The hIOmon Disk I/O Ranger Display was not able to successfully retrieve the name of the Filter Selection that is currently loaded/activated due to the indicated error shown within the error message.
  
  

• HRCMD388E.  The hIOmon Disk I/O Ranger Display was not able to successfully retrieve the Device Summary filter for the currently selected Filter Selection due to the indicated error shown within the error message.
  
  

• HRCMD400E.  An invalid device name was detected by the hIOmon Disk I/O Ranger Display while retrieving the settings (i.e., the various configurable options that are preserved between invocations of the hIOmon Disk I/O Ranger Display).  Please see the " Monitored device/file: " input description above for valid device name specifications.
  
  

• HRCMD420E.  An invalid device name or physical disk number (for which hIOmon metrics are to be retrieved) was specified.  Please see the "Monitored device/file:" input description above for valid device name specifications.
  
  

• HRCMD422E.  An invalid full path file name (for which hIOmon metrics are to be retrieved) was specified.  Please see the "Monitored device/file:" input description above for valid file name specifications.
  
  

• HRCMD430E.  The hIOmon Disk I/O Ranger Display encountered conflicting configuration parameters when retrieving the settings (i.e., the various configurable options that are preserved between invocations of the hIOmon Disk I/O Ranger Display).
  
  

• HRCMD433E.  The hIOmon Disk I/O Ranger Display encountered conflicting configuration parameters when retrieving the settings; more specifically, the configured export metric field was not found.
  
  

• HRCMD434E.  The hIOmon Disk I/O Ranger Display encountered conflicting configuration parameters when retrieving the settings; more specifically, the configured export metric field selection type is invalid.
  
  

• HRCMD435E.  The hIOmon Disk I/O Ranger Display encountered conflicting configuration parameters when retrieving the settings; more specifically, exporting was enabled, but either no export file name or export field names were specified.
  
  

• HRCMD450E.  An invalid number was entered for the refresh interval configuration option/setting.  Please enter a positive number, which represents the number of seconds for the refresh time interval (i.e., the number of seconds between refreshes/updates of the displayed metrics).
  
  

• HRCMD460E.  The retrieval from the hIOmon Manager of I/O operation performance metrics failed because the hIOmon client message buffer used to communicate with the hIOmon Manager is too small.  Consequently, a script prompt is displayed that allows you to set a larger buffer size.  Note that restarting the hIOmon Manager service might be required for this buffer size change to take effect.
  
  

• HRCMD463E.  An invalid value was specified in response to the script prompt for a larger hIOmon client message buffer size.
  
  

• HRCMD465E.  The request to change the size of the hIOmon client message buffer encountered an error.   Additional error message information may help further identify the cause of this error.
  
  

• HRCMD470W.  The idle time associated with a Power Suspend time period is not explicitly accounted for within the idle time and response time metrics accumulated by the hIOmon I/O Monitor.  As a result, abnormal and incorrect response time values might be displayed.

  This condition can be cleared by loading/activating the Filter Selection; note, however, that all of the summary metrics will subsequently be reset to zeroes as a result of loading/activating the Filter Selection and a new Observation Period will begin.

  This condition can also be avoided by including a filter within the loaded/active Filter Selection that specifies a physical device.  For additional information, please see the "System Power Suspension/Resume Considerations" section within the "hIOmon User Guide" document (HMG-1093). 
  
  

• HRCMD485E.  The hIOmon Disk I/O Ranger Display encountered an error while attempting to display the "Setting" configuration display window.
  
  

• HRCMD520E.  The hIOmon Disk I/O Ranger Display encountered the indicated error when trying to retrieve the desired Filter from the currently loaded/active hIOmon Filter Selection.  Please see the "Filter Selection" description section above for basic information related to the Filter Selection configuration requirements.
  
  

• HRCMD530E.  An error was encountered when retrieving the sorted monitored items.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD531E.  An error message indicating that either the "Ascending" or the "Descending" sort order option or neither (but not both) must be selected.
  
  

• HRCMD533W. A warning (or error) message associated with an event encountered when refreshing the list of sorted monitored items.
  
  

• HRCMD535I.   An information message noting that the pre-processing for the selected hIOmon Manager Export File has started.
  
  

• HRCMD536W. A warning message noting that the pre-processing for the selected hIOmon Manager Export File has already been started.
  
  

• HRCMD537I.   An information message noting that the pre-processing for the selected hIOmon Manager Export File has completed.
  
  

• HRCMD539W. A warning message noting that Display refreshes must first be stopped before changing the metrics retrieval source.
  
  

• HRCMD545E.  The hIOmon Disk I/O Ranger Display detected that the export file which was specified to be stopped (i.e., disabled for exporting) was not the currently active export file (i.e., the export file for which exporting is enabled/activated).
  
  

• HRCMD550E.  The hIOmon Manager Export File to be retrieved is empty.
  
  

• HRCMD555E.  The hIOmon Manager Export File to be retrieved has invalid file contents or is not supported.
  
  

• HRCMD560E.  A read error was encountered while trying to retrieval metrics from the hIOmon Manager Export File.
  
  

• HRCMD563E.  The selected hIOmon Manager Export File was not found.
  
  

• HRCMD565E.  An invalid starting date or time was specified for the hIOmon Manager Export File from which metrics are to be retrieved.
  
  

• HRCMD580E.  When attempting to start/enable exporting to the specified file, the hIOmon Disk I/O Ranger Display detected a mismatch between the selected export metric fields (i.e., the particular Performance Threshold Range Count metric types to be exported) and those already present within the existing export file (for which exporting is be enabled/activated).
  
  

• HRCMD585E.  An error was encountered when trying to retrieve the Coalesce configuration file.
  
  

• HRCMD586E.  No DAILY TOTALS were found when to attempting to coalesce the hIOmon Manager Export Files into WEEKLY summary export files. Enable the Coalesce configuration options to enable DAILY TOTALS reports for the respective monitored item type (i.e., Device, DTSdevice, or Process).
  
  

• HRCMD590I.   This informational message provides a notification that the requested coalescing of hIOmon Manager Export Files has started.
  
  

• HRCMD591I.   This informational message provides a notification regarding the current status of the coalescing operations for the hIOmon Manager Export Files.
  
  

• HRCMD592E.  No month or date column was found within the daily totals as part of the preprocessing of the hIOmon Manager Export Files coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD593E.  An unexpected error was encountered while attempting to create the Coalesced folder at the start of the hIOmon Manager Export Files coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD594E.  An unexpected error was encountered during the hIOmon Manager Export Files coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD595W. This warning message provides a notification that a request to coalesce hIOmon Manager Export Files was submitted while coalescing operations were already in progress.  Consequently, this request was denied and the current coalescing operations continued.
  
  

• HRCMD596E.  The hIOmon Manager Export File being coalesced is missing either the expected month or the date column.
  
  

• HRCMD598E.  An unexpected error was encountered while attempting to retrieve the file names of the hIOmon Manager Export Files to be coalesced.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD600E.  An error was encountered when attempting to invoke the hIOmon I/O Trender Display.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD605E.  An error was encountered when attempting to invoke the hIOmon I/O Trender Display "Setting" window.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD610A.  This message is shown when requesting that a remote computer name or IP address be entered upon the "Settings" window display.  It is generally displayed when the "On-The-Web (OTW)" version of the hIOmon Disk I/O Ranger Display has been started, is configured to connect using the hIOmon REST API request support, and no default remote computer name or IP address has been assigned.
  
  Enter the desired remote computer name or IP address, then click on the "Apply" button.
  
  When using the OTW version of the hIOmon Disk I/O Ranger Display, first set/enable the associated "Save" checkbox to save the specified remote computer name or IP address as the subsequent default to be used when starting the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD612A.  This message is shown when the "On-The-Web (OTW)" version of the hIOmon Disk I/O Ranger Display has been started, is configured to connect using the hIOmon REST API request support, and a default remote computer name or IP address has been assigned.  It is displayed to request confirmation the connection should be made to the shown default remote computer name or IP address.
  
  Click on the "Apply" button to confirm that this connection should be performed.
  
  When using the OTW version of the hIOmon Disk I/O Ranger Display, first set/enable the associated "Save" checkbox to save the specified remote computer name or IP address as the subsequent default to be used when starting the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD613W.  Display refreshes must first be stopped before changing the connection to another remote computer or IP address.  Click the "Stop" button to suspend the display refreshes/retrieval.
  
  

• HRCMD615E.  An error was encountered when attempting to acquire a HTTP request object when performing a hIOmon REST API http request.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD616E.  An error was encountered when attempting to connect or issue a HTTP request when performing a hIOmon REST API http operation.  Additional error message information may help further identify the cause of this error, which can be a network or other transport (including timeout) error.
  
  

• HRCMD618E.  An error was encountered when attempting to parse the response to a HTTP request when performing a hIOmon REST API http operation.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD619E.  The response to a successful hIOmon REST API request was null.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD620E.  An error or unexpected status code was returned in response to a hIOmon REST API request.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD622E.  An error status code was returned in response to a hIOmon REST API connection request.  Additional error message information may help further identify the cause of this error.  Note that the connection failure may be due to an invalid SSL certificate encountered.
  
  

• HRCMD623E.  A hIOmon REST API connection attempt failed.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD630E.  Request to display additional DTS metrics, but no additional DTS metric type was specified/selected.  Select an additional DTS metric type from the drop-down list box of additional DTS metrics available for display.
  
  

• HRCMD640E.  An error was encountered while retrieving the hIOmon configuration script file names.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD642E.  An error was encountered while retrieving the hIOmon REST API Configuration Parameter File names.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD645E.  No valid hIOmon Configuration Script file name was specified when attempting to configure or reconfigure the hIOmon software.
  
  

• HRCMD648E.  An error was encountered while identifying the installation of the hIOmon User-Interface (UI) AddOn software package.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD649E.  An error was encountered while identifying the installation type of the hIOmon software.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD650I.  The settings configuration change action was cancelled.
  
  

• HRCMD652E.  An invalid parameter was detected while attempting to perform a settings configuration change.
  
  

• HRCMD654E.  A Windows Management Instrumentation (WMI) error was encountered while attempting to perform a settings configuration change.
  
  

• HRCMD656E.  The hIOmon Disk I/O Ranger Display was unable to implicitly exclude the hIOmon Manager directory path within the Filter Selection being created or modified.
  
  

• HRCMD659E.  The hIOmon Manager service does not appear to be currently running (and so the hIOmon Disk I/O Ranger Display cannot retrieve the Performance Threshold Range Metrics from the hIOmon Manager).  You can verify whether the hIOmon Manager is currently running by going to the Windows "Administrative Tools", selecting the "Services" option, and viewing the current status of the "hyperI/O hIOmon Manager" service.  Please note that the standard hIOmon software installation process configures the hIOmon Manager service so that it is automatically started when the system is started.
  
  

• HRCMD665E.  An error was encountered while validating the hIOmon User-Interface (UI) AddOn values.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD680E.  An error was encountered while attempting to determine the file path where the hIOmon software is installed.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD681E.  An error was encountered while attempting to retrieve current status information regarding the hIOmon software.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD682E.  An error was encountered while attempting to determine the file names of the extant hIOmon Manager Export Files.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD683E.  An error was encountered while attempting to read an hIOmon Manager Export File as part of coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD684E.  An error was encountered while attempting to coalesce totals for hIOmon Manager Export Files as part of coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD685E.  An error was encountered while attempting to coalesce totals for "Data Transfer Size (DTS)" hIOmon Manager Export Files as part of coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD686E.  An error was encountered while attempting to write a coalesced hIOmon Manager Export File as part of coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD688E.  An error was encountered while preprocessing a daily totals hIOmon Manager Export File as part of coalescing operations.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD800E.  The hIOmon Disk I/O Ranger Display encountered the indicated error while attempting to retrieve the saved settings (i.e., the various configurable options that are preserved between invocations of the hIOmon Disk I/O Ranger Display).
  
  

• HRCMD805E.  The hIOmon Disk I/O Ranger Display encountered the indicated error while attempting to retrieve the saved settings from the web browser cookies (i.e., the various configurable options that are preserved between invocations of the "On-the-Web (OTW)" version of the hIOmon Disk I/O Ranger Display).
  
  

• HRCMD810E.  The hIOmon I/O Trender Display encountered the indicated error while attempting to retrieve the saved settings (i.e., the various configurable options that are preserved between invocations of the hIOmon I/O Trender Display).
  
  

• HRCMD820E.  The hIOmon I/O Trender Display encountered the indicated error while attempting to save the settings (i.e., the various configurable options that are preserved between invocations of the hIOmon I/O Trender Display).
  
  

• HRCMD825E.  The hIOmon Disk I/O Ranger Display encountered the indicated error while attempting to save the settings within the web browser cookies (i.e., the various configurable options that are preserved between invocations of the "On-the-Web (OTW)" version of the hIOmon Disk I/O Ranger Display).
  
  

• HRCMD830E.  An invalid file name was specified for the export file that is to be deleted.
  
  

• HRCMD832E.  A request was made to delete the export file that is currently enabled/activated for exporting; such a request is denied (i.e., the delete is not performed).
  
  

• HRCMD835E.  An invalid file name was specified for the export file for which exporting was to be enabled/activated or stopped.  Please enter simply the file name for the export file; the hIOmon Disk I/O Ranger Display application will automatically append a file extension of ".csv" (for the "Comma-Separated-Values" format of the export file) and the file will reside within the same folder/directory from which the hIOmon Disk I/O Ranger Display application was started.
  
  

• HRCMD838E.  The hIOmon Disk I/O Ranger Display application detected that no export metric fields (i.e., Performance Threshold Range Metric types) were selected/defined for the export file that was to be started (i.e., the file to which exporting was to be enabled/activated); consequently, the attempt to start/activate exporting to the export file failed (and exporting was not started/activated).
  
  

• HRCMD839E.  The hIOmon Disk I/O Ranger Display application detected an attempt to start a previously enabled/activated export file for which subsequent changes in the particular Performance Threshold Range Metric types to be exported (i.e., the export metric fields) have also been requested.

Please note that a previously enabled/activated export file must first be stopped (if currently active) and then deleted before you can change (i.e., add and/or remove) the export metric fields selected to be included within the export file.

• HRCMD845E.  A change to the specific export metric fields (i.e., the particular Performance Threshold Range Metric types) selected to be included within the export file was requested for an enabled/active and/or existing export file; please note that exporting to an export file must be stopped/disabled and then the export file deleted before a change can be made to the selected export metric fields that are to be included within the export file.
  
  

• HRCMD850E.  An invalid device or file name was specified while attempting to modify the specified Filter Selection (i.e., either add or remove a filter).  Please see the "Monitored device/file:" input description above for valid device and file name specifications.
  
  

• HRCMD853W.  The display cannot be started due to no monitored item has been selected for display.
  
  

• HRCMD855E.  An error was encountered while attempting to modify the specified Filter Selection (i.e., either add or remove a filter).  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD860E.  An invalid name was specified for the Filter Selection to be loaded/activated.
  
  

• HRCMD863E.  An invalid filter was specified within the Filter Selection to be loaded/activated; as a result, the Filter Selection was not loaded/activated.
  
  

This error can be due to a filter present within the Filter Selection that specifies a device name for a device type which is not supported (e.g., a DVD).  Please check the Application Event Log for hIOmon entries (e.g., with a Source of "hIOmonGr") that provide additional error information.

• HRCMD865E.  An attempt was made to delete a Filter Selection, but there are no Filter Selection present/extant.
  
  

• HRCMD867E.  An invalid name was specified for the Filter Selection to be assigned as the "default" Filter Selection.
  
  

• HRCMD868E.  An invalid name was specified for the Filter Selection to be deleted.
  
  

• HRCMD869E.  An attempt was made to assign a Filter Selection as the "default" Filter Selection, but there are no Filter Selection present/extant.
  
  

• HRCMD890I.  The currently loaded/active Filter Selection (whose name is also shown) has been changed; please re-load/activate this Filter Selection so that the changes made to the Filter Selection can take effect.
  
  

• HRCMD895E.  An error was encountered while attempting to read the selected hIOmon Manager Export File.
  
  

• HRCMD900E.  The hIOmon Disk I/O Ranger Display encountered the indicated error when attempting to connect to the hIOmon WMI Support.  Ensure that the hIOmon software was successfully installed and that the hIOmon Manager service is running.
  
  

• HRCMD910E.  An error was encountered while attempting to activate the specified "hIOmon Key" value.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD915E.  An error was encountered while loading the specified hIOmon ETW I/O Monitor.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD918E.  An invalid hIOmon ETW I/O Monitor type was specified for the hIOmon ETW I/O Monitor unload request.
  
  

• HRCMD920E.  An error was encountered while attempting to determine whether the requested hIOmon ETW I/O Monitor type is currently loaded.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD923E.  An error was encountered while attempting to retrieve the full file path for requested ETW Log file.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD924E.  An error was encountered while attempting to retrieve the "I/O Count Delay" value for the requested hIOmon ETW I/O Monitor.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD925E.  An error was encountered while attempting to retrieve the "Retrieval Time Delay" value for the requested hIOmon ETW I/O Monitor.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD926E.  An error was encountered while attempting to retrieve the "Starting Date/Time" value for the requested hIOmon ETW I/O Monitor.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD928E.  An error was encountered while attempting to determine whether the specified ETW Input Log File is closed.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD929E.  An error was encountered while attempting to determine whether the specified ETW Input Log File is currently active.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD930E.  An error was encountered while attempting to determine whether a hIOmon Filter Selection is currently loaded within the specified ETW I/O Monitor.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD931E.  The hIOmon ETW I/O Monitor must be reloaded/started in order to successfully load a hIOmon Filter Selection or activate logging.
  
  

• HRCMD932I.  First enter any "Retrieval delay options", then click "Load" to load a new hIOmon ETW I/O Monitor using the selected ETW input log file.  Also note that a non-zero "I/O operation count delay" value is ignored if the "Retrieval time delay" value is zero.
  
  

• HRCMD933W.  The specified hIOmon ETW I/O Monitor is already loaded.
  
  

• HRCMD934I.  The selected hIOmon ETW Monitor Input Log file was successfully loaded; click "Configure" to activate.
  
  

• HRCMD935I.  Click the "Metrics for monitored:" radio buttons to populate the monitored-items dropdown list boxes, select a monitored-item to be displayed, then click the "OK" button to refresh the main display with metrics for the selected monitored item.
  

• HRCMD936E.  An invalid hIOmon ETW I/O Monitor Input Log filename value was specified.
  
  

• HRCMD937E.  An invalid hIOmon ETW I/O Monitor "I/O Count Delay" value was specified.
  
  

• HRCMD938E.  An invalid hIOmon ETW I/O Monitor "Retrieval Time Delay" value was specified.
  
  

• HRCMD939E.  An invalid hIOmon ETW I/O Monitor "Starting Date/Time" value was specified.
  
  

• HRCMD940E.  An invalid hIOmon ETW I/O Monitor Output Log filename value was specified.
  
  

• HRCMD941E.  An error was encountered while attempting to retrieve the currently configured maximum allowed number of files for which the hIOmon I/O Monitor can concurrently maintain I/O operation performance metrics.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD943E.  An error was encountered while attempting to retrieve the hIOmon I/O Monitor interfaces supported.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD945E.  An error was encountered while attempting to retrieve the hIOmon I/O Monitor types currently active/loaded.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD946E.  An error was encountered while attempting to access a hIOmon I/O Monitor.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD948E.  An error was encountered while attempting to retrieve the expiration date for the hIOmon software.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD949I.   This information message provides the number of days remaining before the hIOmon software expires.  The message will be displayed by the hIOmon Disk I/O Ranger Display application when it is started, beginning four days before the expiration date is reached.   

When the hIOmon Manager has detected that the expiration date has been reached, it will write an entry (Event ID 499, Source hIOmonGr) to the Application Event Log noting that the trial use of the hIOmon software has expired; the hIOmon Manager will then terminate its processing.

• HRCMD950I.   This information message provides notification that the request to activate the specified hIOmon Key was successfully performed.
  
  

• HRCMD951E.  An error was encountered while processing the request to activate the specified hIOmon Key.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD953E.  An error was encountered while attempting to retrieve product information regarding the hIOmon software.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD955E.  An error was encountered while attempting to retrieve installation information regarding the hIOmon software.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD960E.  An error was encountered while attempting to write to the specified export file.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD965E.  An error was encountered while attempting to delete the specified export file.  Additional error message information may help further identify the cause of this error.
  
  

• HRCMD970E.  An invalid/missing device name was detected during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD971E.  An error was encountered while attempting to verify that the named Filter Selection was successfully assigned as the default Filter Selection during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD973E.  An error was encountered while creating a Filter Selection during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display.  Both the name of the Filter Selection and the device name of the filter included within the Filter Selection are also shown within the error message.
  
  

• HRCMD974E.  An error was encountered while attempting to start logging within the hIOmon I/O Monitor during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD975E.  An invalid Filter Selection name was detected during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD976E.  An error was encountered while loading/activating the named Filter Selection during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD977E.  An error was encountered while verifying the named Filter Selection was successfully loaded/activated during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display.
  
  

• HRCMD978E.  An invalid Filter Selection name was detected while attempting to assign the named Filter Selection as the default Filter Selection during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display
  
  

• HRCMD979E.  An error was encountered while attempting to assign the named Filter Selection as the default Filter Selection during the initial configuration processing performed by the hIOmon Disk I/O Ranger Display
  

Copyright © 2011-2024  hyperI/O LLC.  All Rights Reserved.