A quick word of caution when monitoring I/O operations at either the physical volume level or the physical device level as regards the process-related metrics:

As previously noted, the hIOmon software can (concurrently) capture I/O operation performance metrics at three distinct levels within the I/O stack within the operating system:

1) The file-level (logical drive/disk)
2) The physical volume level, and
3) The physical device level (which is similar to the "PhysicalDisk" level in the Windows Performance/System Monitor).

It is important to note that I/O operation performance metrics at the file-level are observed by the hIOmon I/O Monitor within the context of the particular process that initiated the respective I/O operation. Consequently, the process-related metrics (e.g., the "process name") associated with the other respective metrics do reflect what the particular process did/experienced in terms of I/O activity.

However, it is another story further down at the physical volume and physical device levels. In the case of I/O operations at either of these levels within the operating system, the hIOmon I/O Monitor observes the I/O operations within an essentially indeterminate context.

That is, the "process/thread" currently running at the time during which the hIOmon I/O Monitor observes the I/O operation could be for any process (and not necessarily for the particular process that initiated the "originating" I/O operation up at the file-level).

What this all means is that if you only configure the hIOmon software to monitor I/O operations at either the physical volume and/or physical device levels, then you need to be cautious about which particular process is identified with a respective set of I/O operation metrics.

Now in these cases the metrics reported do accurately reflect the particular process that was "running" when the hIOmon I/O Monitor observed the respective I/O operation (but again, this process is not necessarily the one that initiated/originated the I/O operation).

So overall then, if you are interested in capturing I/O operation performance metrics related to specific processes in general, then you need to collect I/O operation performance metrics at the file-level (so that the hIOmon I/O Monitor can initially observe the I/O operations within the context of the particular process that initiated the I/O operations).

Note too that the hIOmon software also provides a "Physical Device Extended Metrics" option, whereby if you have configured the hIOmon software to capture such metrics and to concurrently monitor also at the physical volume and/or physical device levels, then it can automatically correlate the I/O operations performed at these levels with those at the upper file-level. Basically this enables you to associate the physical volume/device I/O operations with their respective process (which again, cannot be done - in general - by monitoring only at the physical volume and/or physical device levels as noted above).

The reason I said "in general" is that there are applications that essentially bypass performing their I/O operations at the file-level, but instead initiate them directly at either the physical volume or physical device level within the operating system - but this is another whole story.

Hopefully the above is clear.

And perhaps another key take-away here is that the "flow" of I/O operations through the I/O stack of the operating system is not as "simple" as maybe some presume.