Brief help information for the following topics related to the hIOmon Disk I/O Ranger Display application (HTA) is provided below:
Background Information
The hIOmon "Disk I/O Ranger Display" application can be used to display the hIOmon "Performance Threshold Range Metrics", which are a selected set of summarized I/O operation performance metrics that are specifically focused upon the ranges of I/O operations per second (IOPS), megabytes-per-second (MB/s) data transfer rates, response time (RT), I/O operation queue depths/lengths (QD), and data transfer sizes/lengths (DTS) actually observed by the hIOmon I/O Monitor for individual files, devices, and processes.
The IOPS, MB/s, QD, and RT metrics are automatically included within the summarized I/O operation performance information collected by the hIOmon software. The DTS summarized metrics are optionally collected separately. Also note that the capture of the hIOmon "Performance Threshold Range Metrics" does not require I/O operation trace collection.
All of these metrics can also be displayed by the hIOmon Presentation Client, the hIOmon CLI, and the hIOmon WMI Browser, all of which are included within the "hIOmon I/O Performance Monitor" software package from hyperI/O. These metrics can additionally be accessed via the hIOmon WMI Support.
The hIOmon “Performance Threshold Range Metrics” can also be directly exported to a CSV-formatted "hIOmon Manager Export File", which is another feature that is included within the "hIOmon I/O Performance Monitor" software package.
In addition, the hIOmon Presentation Client can be used to display these metrics within a “Bar Chart” graphic
format similar to that shown by the hIOmon
"Disk I/O Ranger Display" application.
Please note that the hIOmon "Performance Threshold Range Metrics” reflect the
actual I/O operation activity observed by the hIOmon I/O Monitor
software component. For instance, the
"IOPS < 100" Range Count for read I/O operations reflects the number of one-second intervals during which the hIOmon I/O Monitor actually observed a total number of monitored read I/O operations that was less than 100 read I/O operations.
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).
Also note that the hIOmon "Disk I/O Ranger
Display"
application displays the selected Performance Threshold Range Metrics in real-time.
That is, the current summarized values of these metrics (as maintained by the
hIOmon I/O Monitor) are retrieved by the hIOmon "Disk I/O Ranger
Display" application from the hIOmon I/O Monitor and then displayed.
This display is repeatedly refreshed (i.e., the latest values are retrieved from
the hIOmon I/O Monitor and then displayed) upon a user-selected periodic basis
(e.g., every five seconds).
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" application also supports the display and export of the hIOmon "DataTransferred/Time Index" metric, which 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"
The hIOmon "Disk I/O Ranger Display" application is run as a Microsoft Windows HTML Application (HTA). The metrics displayed are those currently collected by the hIOmon I/O Monitor, which must be properly configured to collect the particular types of metrics displayed by the hIOmon "Disk I/O Ranger Display" application. See the section immediately below for the configuration requirements.
Configuration Information
The hIOmon software must be properly configured in order to collect the "Performance Threshold Range Metrics" for display by the hIOmon "Disk I/O Ranger Display" application. This proper configuration includes an active/loaded hIOmon "Filter Selection". The hIOmon "Filter Selection" specifies the particular files/devices that are to be monitored by the hIOmon software 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 files and logical devices, physical volume(s), and/or physical device(s) of interest.
Please note that the "summary" metrics collected by hIOmon are summarized I/O operation performance metrics which are automatically aggregated by the hIOmon I/O Monitor at the time that it observes the individual I/O operations. Moreover, the collection of these "summary" metrics does not require the collection of "I/O operation trace" data (which is a separate option also provided by the "hIOmon I/O Performance Monitor" software package). The "summary" metrics are an unique feature of the hIOmon software.
The hIOmon "Disk I/O Ranger Display" application 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 the hIOmon I/O Monitor.
Please note that this application also provides a limited means to configure the hIOmon software so as to collect the summary metrics required for display. Additional information is provided within the "Getting Started" section below.
In addition, a hIOmon client (e.g., the hIOmon Presentation Client, the hIOmon WMI Browser, etc.) can be used to configure more specifically the hIOmon software in accordance with particular monitoring requirements; please note that these clients are included with the "hIOmon I/O Performance Monitor" software package.
The various hIOmon "Add-Ons" that are included with the "hIOmon I/O Performance Monitor" software package can also be used to quickly and easily configure the hIOmon software so as to meet particular configuration requirements. For example, the hIOmon "SSD I/O Performance Metrics Analysis Add-On" uses a series of interactive input prompts that allow you to simply specify the particular physical volumes and/or physical devices for which the hIOmon software is to collect SSD TRIM-related metrics (and optionally summary metrics for read and write I/O operations, including the "Performance Threshold Range Metrics"). Based upon your selected input parameters, this hIOmon Add-On will then automatically configure the hIOmon software; please note that a restart/reboot of the computer system might be required in order to activate the required hIOmon configuration changes.
Installation Information
The hIOmon “Disk I/O Ranger Display” application can be found in the “hIOmonDiskIORanger” folder within the “..\hyperIO\hIOmon\Support\AddOns\” directory where the hIOmon software was installed; this applies to both the "hIOmon Disk I/O Ranger" and the "hIOmon I/O Performance Monitor" software products.
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).
To use/run the hIOmon "Disk I/O Ranger Display" application, 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.
You can also run the hIOmon “Disk I/O Ranger Display” application by simply double-clicking upon the "hIOmonDiskIORanger.hta" file located within the “hIOmonDiskIORanger” folder as noted above within the "Installation Information" section.
When first run after the installation of the hIOmon 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, which should not be the case if you have not yet used any of the hIOmon clients (e.g., the hIOmon Presentation Client, the hIOmon WMI Brower, etc.) or a hIOmon Add-On to configure the hIOmon software.
If no active Filter Selection is found, then the hIOmon Disk I/O Ranger Display application will automatically perform the following steps:
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 "C:" logical drive 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.
In
addition, "Device Summary" metrics will also be collected for the
"C:" logical drive; these "Device Summary" metrics
reflect the combined totals for all of the monitored files that reside upon
the C: logical disk and for which the hIOmon I/O Monitor observed read
and/or write I/O operations.
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 physical
disk associated with the "C:" logical drive. 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.
After successfully creating this "IORangerFS" Filter Selection, the hIOmon Disk I/O Ranger Display application will then load/activate this Filter Selection. The hIOmon I/O Monitor will immediately begin monitoring I/O operations for files residing upon the C: drive and collecting summary metrics; please note that no reboot of the system is required in this case since the hIOmon I/O Monitor will not be monitoring I/O operations at either the physical volume level or physical device level within the Windows OS I/O stack.
Please note that no reboot of the system
will be required unless you requested (in step 3 above) that I/O operation
performance metrics are also to be collected for the physical disk associated with
the C: drive. If you did request that physical device metrics also be
collected, then you will need to restart the system in order to complete the
configuration of the hIOmon software; the hIOmon I/O Monitor will be able to
monitor
I/O operations at the physical device level
within the Windows OS I/O stack after the system has been restarted.
If you do not restart the system in this case, then an error message
will be shown when you try to display I/O operation performance metrics for
the physical device.
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 Response Time (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".
The Main Display includes the optional detailed display of four basic "Performance Threshold Range Metric" groups (i.e., the IOPS, MBs, Queue Depth (QD), Response Time (RT), and Data Transfer Sizes (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.
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).
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 volume or 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" 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 < 100: 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 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.
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 < 100") was observed by the hIOmon I/O Monitor.
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 (MBS) 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.
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.
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.
Also note that for first QD Range Count only (i.e., "QD > 1"), a percentage is also 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.
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.
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).
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, the other hIOmon clients (e.g. the hIOmon Presentation Client, the hIOmon WMI Browser, etc.) that are included within the hIOmon I/O Performance Monitor software package 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 volume and/or 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 Presentation Client, the hIOmon WMI Browser, etc.) that are included within the hIOmon I/O Performance Monitor software package.
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. 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 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:
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 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.
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.
The metrics are displayed
upon a individual monitored item basis (i.e., for a single
file, process, logical disk, physical volume, or physical device). The
"Settings"
button/option can
be used to
select a different monitored item for which the metrics are to be
displayed.
The display of the metric
values is periodically refreshed/updated automatically to the current values.
You can view the refresh time interval by clicking on the "Settings"
button/option; the "Settings" options can also be
used to select a different refresh time interval. Also please
note that only those IOPS, MBs, QD, RT, and DTS Range Counts that have a non-zero value are
displayed.
An error indication
will be displayed near the bottom of the Main Display in the
event that the hIOmon Disk I/O Ranger Display application encounters an
error. Click on the "Settings" option/button to view additional
details about the error.
If a Filter Selection change
is made while the hIOmon Disk I/O Ranger Display
application is active
(i.e., is running), then the hIOmon Disk I/O Ranger
Display application will subsequently display the selected metrics
for the new Observation Period.
You can invoke/run more than one instance of the 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, physical volume, or physical device).
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).
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 volume/device name are the drive letters of the particular Logical Disks that are associated with the respective physical volume/device.
Lastly, please note that the specified physical volume (or physical
device) represents a physical volume (or 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).
Seconds between refreshes. This input text field enables you to specify the time interval between refreshes/updates 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). Also note that stopping the refresh update of the Main
Display does not stop of the collection of I/O operation performance
metrics by the hIOmon I/O Monitor.
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, two additional values and percentages are displayed for the IOPS Range Counts. A second percentage (and associated value) is displayed that shows 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 third 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. The first percentage that is always shown for IOPS Range Counts is described above.
MBs data transferred: When this checkbox is selected/enabled, a second percentage (and associated value) is displayed that shows for MBs Range Counts only, 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. The first percentage that is always shown for MBs Range Counts is described above.
RT data transferred: When this checkbox is selected/enabled, a third percentage (and associated value) is displayed that shows for RT Range Counts only, 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.
A fourth percentage shown (for RT Range Counts only) 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).
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.
Monitored device/file. 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 device or file 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 application 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 application 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 application 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
To monitor a specific physical volume, you can simply the letter of a Logical Drive associated with the physical volume along with the physical volume alias character (a question mark: "?"); for example: C?
Also please note that the system may need to be rebooted as a result of adding a filter for a physical volume or a physical device. If a system reboot is required, the hIOmon Disk I/O Ranger Display application will display a message saying that a system reboot is required. Monitoring of the physical volume/device will not be successful until the restart/reboot is performed.
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 application 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 summary metrics is enabled are highlighted with an almond 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 Presentation Client or 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 application; however, other hIOmon clients (e.g. the hIOmon Presentation Client, the hIOmon WMI Browser, etc.) that are included within the hIOmon I/O Performance Monitor software package 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: 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.
Also please note that the system may need to be rebooted if the Filter Selection to be loaded/activated contains filters that specify a physical volume or a physical device to which the hIOmon I/O Monitor is not currently attached. If a system reboot is required, the hIOmon Disk I/O Ranger Display application will display a message saying that a system reboot is required. The loading/activation of the specified Filter Selection and the monitoring of the physical volume/device will not be successful until the restart/reboot is performed.
Delete: To explicitly delete a specific Filter Selection, first select the respective Filter Selection withinthe 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: 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.
Max Allowed File Count. 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 application 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.
Export metrics to file: 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 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.
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 application 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 two special items within the drop-down list box: SelectALL and SelectDisplayedRCtypes.
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 application. Moreover, if an export file is enabled/active at the time that you exit the hIOmon Disk I/O Ranger Display application, then the same export file will automatically be started (with the same selection settings) by the hIOmon Disk I/O Ranger Display application the next time you start the application.
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 application 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
application.
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.
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 application. 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.
The following error messages can be displayed by the hIOmon Disk I/O Ranger Display application:
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 has been uninstalled (e.g.,
as part of the uninstall/removal of the hIOmon software).
HRCMD150W.
Either no
physical volumes/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 volume(s)/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 volume/device is selected for which metrics are to be
displayed. Please select the particular physical volume/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 volume/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 volume/device of
interest within the "Process Names" drop-down box list.
HRCMD250W. No metrics were available for retrieval for the logical device or physical volume/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 or physical volume, 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/device/process 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
application 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
application detected that the export file specified to be deleted was not
found.
HRCMD330E. The
hIOmon Disk I/O Ranger Display
application 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
application 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).
HRCMD350E. The
hIOmon Disk I/O Ranger Display
application 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, physical volumes 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
application 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
application 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
application 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
application 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.
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.
HRCMD365W. 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.
HRCMD380E. The
hIOmon Disk I/O Ranger Display
application 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
application 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
application 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
application 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.
HRCMD400E. An
invalid device name was detected by the
hIOmon Disk I/O Ranger Display
application while retrieving the settings (i.e., the various configurable options
that are preserved between invocations of the hIOmon Disk I/O Ranger Display
application). 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
application 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
application).
HRCMD433E. The
hIOmon Disk I/O Ranger Display
application 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
application 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
application 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).
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 either a physical volume or 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
application encountered an error while attempting to display the
"Setting" configuration display window.
HRCMD520E. The
hIOmon Disk I/O Ranger Display
application 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.
HRCMD545E. The
hIOmon Disk I/O Ranger Display
application 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).
HRCMD580E. When
attempting to start/enable exporting to the specified file, the
hIOmon Disk I/O Ranger Display
application 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).
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.
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
application 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
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.
HRCMD800E. The
hIOmon Disk I/O Ranger Display
application 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
application).
HRCMD820E. The
hIOmon Disk I/O Ranger Display
application encountered the indicated error while
attempting to save the settings (i.e., the various configurable options that
are preserved between invocations of the hIOmon Disk I/O Ranger Display
application).
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.
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.
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.
HRCMD900E. The
hIOmon Disk I/O Ranger Display application 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.
HRCMD940E. 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.
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.
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 application.
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 application.
HRCMD973E. An
error was encountered while creating a Filter Selection during the initial
configuration processing performed by the hIOmon Disk I/O Ranger Display
application. 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.
HRCMD975E. An
invalid Filter Selection name was detected during the initial configuration
processing performed by the hIOmon Disk I/O Ranger Display application.
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 application.
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 application.
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
application.
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 application.
Copyright © 2011-2013 hyperI/O LLC. All Rights Reserved.