Hi,
I have triggers that report low disk space on a bunch of servers. The trigger uses percentage item for free space (vfs.fs.size[/,pfree]) and activates when the value drops below 10%. So far so good - the trigger works as expected. This trigger is hooked on action that sends email with following content:
The problem is that the free space in bytes (the last line) is reported incorrectly. The value is way too low than actual free space. I used to use v.1.4.2 where the value was reported in bytes (w/o M, G unit) in the email and it was correct. The problem started when I upgraded to 1.4.5. Now the values are reported in MB or GB and they are wrong.
Does anyone have such problem? Or am I missing something obvious?
Thank you!
I have triggers that report low disk space on a bunch of servers. The trigger uses percentage item for free space (vfs.fs.size[/,pfree]) and activates when the value drops below 10%. So far so good - the trigger works as expected. This trigger is hooked on action that sends email with following content:
Code:
Hostname: {HOSTNAME}
IP: {IPADDRESS}
Free space (percent) : {{HOSTNAME}:{TRIGGER.KEY}.last(0)}
[B]Free space (bytes): {{HOSTNAME}:vfs.fs.size[/,free].last(0)} b[/B]
Does anyone have such problem? Or am I missing something obvious?
Thank you!
Comment