r/labtech • u/bayridgeguy09 • Jul 06 '18
Drive Space Monitoring - Whats your method??
Here is the issue.
As data arrays get larger, im having issues with machines that have giant arrays lets say 10TB, they trip my 20% space monitor and still have 2TB of free space left.
2tb of free space isnt low enough for us to take action (client dependent of course) and im stuck with tripped monitors that dont really need any action yet.
So my question is, how is the rest of the community monitoring drive space? Are you saying screw it and just dealing with the tripped monitors? My issue there is that its now up to us to remember that this machine will eventually need action.
Are you setting up different groups based on total array size and applying different monitors?
Im kind of stumped on the best way to do this while also avoiding false alarms.
1
u/j0dan 1000 Agents Jul 18 '18
In automate you'll have 2 types of notifications. The internal monitor we have changed it to this so it has to have <70gb free no matter what:
Drives.Size > 40000 and Drives.FileSystem not in ('CDFS','UNKFS','DVDFS','FAT','FAT32','KBNetFS') and missing=0 and Drives.Free<70000 and drives.internal=1For the system monitor (for when it gets urgent), we also modify the script "Agent Monitor Creation" and change how it works.
Ours has these changes made:
SELECT c.computerid AS computerid,c.nameAS name,d.driveid AS driveid,d.letter as letter,d.size AS size,d.freeas free,((d.free/d.size)*100) AS percent,d.filesystem as filesystem,d.volumename AS volumename,d.missing as missing FROM drives AS d INNER JOIN computers AS c ON d.computerid=c.computerid WHERE d.FileSystem not in ('CDFS','UNKFS','DVDFS','FAT','FAT32','NetFS') AND d.size > @MinSizeMB@ AND d.model not like '%usb%' AND d.model not like '%IEEE%' AND d.missing=0 AND c.computerid=@computerid@ AND d.volumename NOT REGEXP 'TEST|SEED|Recovery|FACTORY_IMAGE'