Switch to using perf counters to get disk io metrics on Windows #1340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Disk IO stats returned by gopsutil on Windows are dependent on the drive configuration and don't always work (e.g. doesn't work on EC2 or GCE). Even if we fixed this to work like psutil, the drive descriptions will show as PhysicalDisk[0-26] instead of reflecting the associated partition mounts [A-Z]: and there is no straightforward way to show a more user friendly name.
Without any better alternative, this PR reverts to getting Disk IO stats from performance counters on Windows. There doesn't seem to be a performance counter for "Disk Time" so ignoring that for now.
Note this PR renames the
disk_scraper.go
todisk_scraper_others.go
(otherwise unchanged) & puts that behind a!windows
build flag. We then add a separate scraper for windows,disk_scraper_windows.go
, with an implementation using perf counters.