We love (and sometimes cuss at) Zenoss but are working to improve the great work put into the some of the Zenpacks we depend on like the Window WMI related ZenPacks. 

One of the key components of our monitoring system is the stats on available drive space... for alerts of low disk space and also trend information for predictive analysis of 'drive full' issues, hints something is wrong (sudden jump or fall in disk space usage), and capacity planning.

Unfortunately, since moving to Zenoss 4.2.0 we have not been able to get the WMI/Windows drive usage stats to work properly at all.  The linux command and SNMP modelling works great.  So we are diving in to try and get this important piece sorted out.

Attached is our initial "quick" fix for the WMI FileSystemMap implementation.  This provides the following changes to the current FileSystemMap for the WMI modelling:

1) Modelling and stats collection of Used Bytes and Free Bytes now works - but ONLY for Windows NFTS drives formatted to 4096KB block sizes (Windows default)

* the problem with the current drive space stats seems to be the blocksize 'guess' mechanism since Windows does not provide an easy way to get this info.  For an initial quick fix, since almost all our monitored Windows systems use the default 4096KB allocation unit (blocksize), we just hard-coded the block size calc to use 4096.   We are still working on a better way to do this rather than hard-coded blocksize

.

2) The formating of the drive information labels has been cleaned up (to our preferences) so it shows

     Drive letter:  Volume name  (Serial No.: ###...)

     eg   D:  Data Drive  (Serial No: C835434D5)

3) Automatically ignores any drive names of "System Reserved" which eliminates the small 100MB boot/system partion in Windows 7/2008

4) Automatically ignores any drive volumes which start with "//?/" which is what non-native or raw partitions show up as (such as USB drives for Windows backup, some inaccessible but connected SAN volumes, etc.)

To implement our fix just replace (recommend to cp a backup copy of the original files first) the following two files in ZENOSS  then restart ZENOSS:

FileSystemMap.py (source)

FileSystemMap.pyc (compiled python binary)

The standard ZENOSS folder location is:

/opt/zenoss/ZenPacks/ZenPacks.zenoss.WindowsMonitor-1.0.2-py2.7.egg/ZenPacks/zenoss/WindowsMonitor/modeler/plugins/zenoss/wmi

After copying the files, restart Zenoss with "service zenoss restart"

If you find the changes do not appear, you may need to remove the cached python binary file.  To do this, navigate to the above wmi folder and delete the temp file with:  "rm FileSystemMap.py~"

you can also download these two files from here:

http://www.cordeos.com/downloads/zenoss/FileSystemMap.zip

We will appreciate any comments or cooperative assistance to impove this great open source project.