Template for monitoring disk space on Windows server

[mihab]

Hi

Is there available template that I can simply import and set so that Zabbix will check disk space (via agent not from SNMP) and send e-mail when disk space is lower than configured ?
Or can anyone please explain me (step-by-step please for dummies ) how can this be set-up manually ?
Thanks
Mike

[LenR]

The template provided with the install will discover windows disks and has triggers for > 20% free space. Adding an Action would be needed to do the notifications.

I'm not sure what you mean by "disk space is lower than configured", if your disks total size changes, you have an odd environment, but you could define a similar trigger on total drive size and the change function

https://www.zabbix.com/documentation/2.4/manual/appendix/triggers/functions

[Linwood]

If by configured you mean you want different values on different servers, just replace the .8 or .2 in the default with a macro.

Incidentally CD and DVD drives are an issue in SNMP (Haven't checked the agent template), you might want to have the trigger check for total space greater than 10G or so to eliminate them, if they aren't already eliminated.

[mihab]

Hi

On Windows server I have two partitions C and D.
C in 100GB, D is 200GB
I want to configure zabbix that will send me an e-mail when
C partition disk space is lower than 10GB
D partition disk space is lower than 20GB

How can this be done ?
Thanks
Mike

[alientm]

Read this manual

http://www.catonrug.net/2014/10/create-trigger-free-disk-space-is-less-than-n-gb-zabbix.html

[Linwood]

C in 100GB, D is 200GB
I want to configure zabbix that will send me an e-mail when
C partition disk space is lower than 10GB
D partition disk space is lower than 20GB

Since that's just 10% that's easily done by changing the trigger (edit the .8 to .9), or change to a macro which you set to 10 or 90 as you prefer.

However, just to complete the story, what is much harder is if you said you wanted to monitor C to 10GB and D to 15GB, i.e. arbitrary percentages. in that case directly cloning the trigger and editing it as host specific is probably the best bet, as Macros can only be applied at the host level.

The sad fact is that in any big organization you often have disks that are routinely more full than others (or that should be routinely less full). For example, on a NVR (security cameras) system that purges as it adds new footage, there's no point in running less than say 95% full, as the rest of the space is just wasted. These kind of exceptions are a bit painful and have to be dealt with at the trigger level, not really the host level nor the template level.