banshee/windows-collection/windows/snmp/
volumes
The space of each fixed volume of a Windows, and when it will be full, by SNMP
par banshee1 installation2 versions
v2Dernière
Publiée le 28 octobre 2026. One naming convention across collections; documentation completed.
Volumes of a Windows, by SNMP
Returns, for each fixed volume of a Windows (C:`, D:`, a mount point), its size, the space used, the free space and the share used. Four watches are proposed, each one set on the probe, among them the volume that will be full within a week.
Versions
Generic: written for the SNMP agent of Windows, the feature "SNMP Service" of Windows Server or the optional feature of Windows 10 and 11, and for HOST-RESOURCES-MIB, which it serves. That every release of Windows serves it alike is assumed, not yet checked on a real Windows.
How it works
The collector reads the table hrStorageTable of HOST-RESOURCES-MIB: hrStorageType (1.3.6.1.2.1.25.2.3.1.2), hrStorageDescr (.3), hrStorageAllocationUnits (.4, in bytes), hrStorageSize (.5) and hrStorageUsed (.6, both in allocation units).
- It keeps the rows of the type
hrStorageFixedDisk(1.3.6.1.2.1.25.2.1.4) only. Network drives, removable drives and optical drives are of other types, and are left out by the code itself, not by the selection: a drive letter does not say whether the drive is a network one. The type is an OID, accepted with or without a leading dot. - A row of zero size (a volume not mounted, not formatted) is left out: it has no space to judge.
- The name of a volume is its description up to " Label:" (Windows writes
C:\ Label:System Serial Number 1a2b3c4d), so `C:`. - The figures are the counts of allocation units times their size, in GiB, rounded to a tenth; the share used is the used over the size.
- Nothing is skipped at the first run.
- A Windows always has at least its system volume: a run that returns no volume (an empty table, a type in a form the pattern does not recognise, no fixed disk of non-zero size) stops the collector as misconfigured, and the message says how many rows were read and which types.
- By default, every volume is watched; the selection is changed on the probe.
Nothing is written to the Windows: SNMP reads only.
Prerequisites
- The SNMP service of Windows, installed and started: - on Windows Server, the feature "SNMP Service" (Server Manager, Add Roles and Features; or
Install-WindowsFeature SNMP-Servicein PowerShell); - on Windows 10 and 11, the optional feature "Simple Network Management Protocol (SNMP)" (Settings, Optional features; orAdd-WindowsCapability -Online -Name SNMP.Client~~~~0.0.1.0in PowerShell). - In the properties of the service "SNMP Service", tab Security: - a community with the right READ ONLY, which banshee reads in
protocol:snmp:v2c:community; - under "Accept SNMP packets from these hosts", the address of the poller. - SNMPv3: the SNMP agent of Windows does not offer it;
protocol:snmp:versionstaysv2c. The community then travels in clear text: keep it read-only and accepted from the poller alone. - The Windows firewall open to the poller on UDP 161 (the rule "SNMP Service (UDP In)").
Outputs
| Name | Label | Unit | Per instance |
|---|---|---|---|
used-percent | Used space | % | yes, per volume |
used | Used space | GiB | yes, per volume |
free | Free space | GiB | yes, per volume |
size | Size | GiB | yes, per volume |
Watches
| Name | Title | Kind | Defaults | Checked by default |
|---|---|---|---|---|
used | Used space | above a threshold, on used-percent | warning above 80 %, critical above 90 % | yes |
full-soon | Full within a week | above a threshold, on used-percent, with a trend | warning when the trend reaches more than 99 % within 7 days; no critical | yes |
free | Little free space | below a threshold, on free | critical below 5 GiB; no warning | no |
missing | Volume missing | expected instances, on used-percent | no volume named: it raises nothing until names are set on the probe | no |
"Full within a week" needs the history of the volume: until the poller has learnt it, the watch says it is learning and raises nothing.
Limits
- The SNMP agent of Windows serves neither the IOPS, nor the throughput, nor the latency of the disks: none of them can be returned here.
- Network drives (mapped letters), removable and optical drives are not volumes here. A USB disk that Windows announces as fixed is counted.
hrStorageSizeholds on 31 bits: a volume of more than 2^31 allocation units (8 TiB in units of 4 KiB) is miscounted by the agent itself.- A volume without a letter nor a mount point is named as the agent describes it.