Describe the solution you'd like
On Windows, psutil's disk_io_counters() returns read_time and write_time in whole seconds instead of milliseconds, so the latency disk-io derives from them is 1000 times too small and nearly always 0.0 ms. Until this is fixed, disk-io no longer reports await on Windows and ignores --await-warning and --await-critical there.
Upstream:
Once a psutil release contains the fix:
- bump psutil in the lockfiles to that release
- report await on Windows again, but only if the installed psutil is at least that release (older versions keep leaving it out)
- on Windows, re-enable the await perfdata, the Await table column and the
--await-* thresholds, and update README and DESCRIPTION
Additional context
Verified on Windows Server 2025 with psutil 7.2.2: 20 s of queue-depth-1 reads took 19.25 s in ReadFile(), the raw IOCTL_DISK_PERFORMANCE ReadTime grew by 17.57 s (100 ns units), psutil's read_time by 17 (documented unit: ms).
Describe the solution you'd like
On Windows, psutil's
disk_io_counters()returnsread_timeandwrite_timein whole seconds instead of milliseconds, so the latency disk-io derives from them is 1000 times too small and nearly always 0.0 ms. Until this is fixed, disk-io no longer reports await on Windows and ignores--await-warningand--await-criticalthere.Upstream:
Once a psutil release contains the fix:
--await-*thresholds, and update README and DESCRIPTIONAdditional context
Verified on Windows Server 2025 with psutil 7.2.2: 20 s of queue-depth-1 reads took 19.25 s in
ReadFile(), the rawIOCTL_DISK_PERFORMANCEReadTimegrew by 17.57 s (100 ns units), psutil'sread_timeby 17 (documented unit: ms).