It appears disk/windows_disk.go filters on drive letters, excluding folder mounted volumes.

As a Telegraf user, I am looking to monitor all disk volumes mounted in Windows, both drive-letter mounted and folder-path mounted. Internally, Telegraf uses gopsutil to retrieve these data. Gopsutil appears to only support drive letters mounted disks.

Additional context

• Closed Telegraf bug: Bug: [[Inputs.Disk]] doesn't include folder mount points in Windows OS influxdata/telegraf#8332

  • Expected behavior: When a volume is mounted to a folder in Windows, the [[inputs.disk]] plugin should output a series for that volume, with the path tag being the path to the folder mount point, and the device tag being either the volume DeviceId or the Disk & Partition numbers.
  • Actual Behavior: Only volumes mounted to drive letters are returned

• To help reproduce this issue without needing a physical device, one can create a small VHD and mount it to a folder. Some potentially helpful links:

  • Locating Mount Points Using PowerShell | Learn Powershell | Achieve More
  • Mount all .vhdx files in a temporary folder : PowerShell
  • Profiling disk mount points with Windows Perfmon | Convergence of Data, Cloud, and Infrastructure
  • powershell - Correlate Physical Device ID to Volume Device ID - Stack Overflow
  • QEMU disk image utility — QEMU 6.2.50 documentation