Actions for Zabbix Disk Discovery

[youngservers]

Hi All,
I have been facing issue of False values in email against Zabbix Disk Discovery Alerts.
It just send first 1 or two values accurate then sends the same old false values.
Any one help me in this old issue, is it a bug or some bad action configurations against disks discovery rules.
Thanks for your time.

[dpeterson]

What version of Zabbix are you running?

[youngservers]

What version of Zabbix are you running?

Hi dpeterson, I am using 2.4.1 version of zabbix and the issue was also there on 2.0.8 version before my upgrade.

[kloczek]

Hi All,
I have been facing issue of False values in email against Zabbix Disk Discovery Alerts.

Ehat exacly meam "disk discovery"? Zabbix does not have any standard disovery items for block devices.
Are you doing some windows host monitoring?
What exactly you are doing and why discovery of some "disks" is causing sending email messages? Why it is not used to generate some items/triggers prototypes?

[youngservers]

Ehat exacly meam "disk discovery"? Zabbix does not have any standard disovery items for block devices.
Are you doing some windows host monitoring?
What exactly you are doing and why discovery of some "disks" is causing sending email messages? Why it is not used to generate some items/triggers prototypes?

Hi kloczek,
I means of Trigger prototypes against the Mounted Filesystem Discovery.
Now, When the trigger prototype reached its threshhold value like "Disk space of file server on D Drive is less than 7.5 %" it generates a Alert from the action.
Now that action continuously repeating after 6 hours.
Then after a day Disk space on Drive lefts 3.7% but the Trigger Prototype generates the same old value i.e 7.5%.
It does not send the alert with latest current value but the Graph shows the Latest data.
I had attached default Template OS Windows to my Windows host in Zabbix.

Key of Item Prototype is:
vfs.fs.size[{#FSNAME},pfree]
Expression of my Trigger Prototype is:
{File-server:vfs.fs.size[{#FSNAME},pfree].last(0)}<7

[kloczek]

Hi kloczek,
I means of Trigger prototypes against the Mounted Filesystem Discovery.
Now, When the trigger prototype reached its threshhold value like "Disk space of file server on D Drive is less than 7.5 %" it generates a Alert from the action.
Now that action continuously repeating after 6 hours.

Trigger generates alarm. "Action" has special meaning in context of the zabbix

https://www.zabbix.com/documentation/2.4/manual/config/notifications/action

Check triggers settings do you have enabled "Multiple PROBLEM events generation". If yes probably you can disable this. Try to read documentation about this if it is your case

https://www.zabbix.com/documentation/2.4/manual/config/triggers/trigger

Then after a day Disk space on Drive lefts 3.7% but the Trigger Prototype
generates the same old value i.e 7.5%.
It does not send the alert with latest current value but the Graph shows the Latest data.
I had attached default Template OS Windows to my Windows host in Zabbix.

Key of Item Prototype is:
vfs.fs.size[{#FSNAME},pfree]
Expression of my Trigger Prototype is:
{File-server:vfs.fs.size[{#FSNAME},pfree].last(0)}<7

OK. What is the Interval on the item with vfs.fs.size[{#FSNAME},pfree] ?

[youngservers]

Trigger generates alarm. "Action" has special meaning in context of the zabbix

https://www.zabbix.com/documentation/2.4/manual/config/notifications/action

Check triggers settings do you have enabled "Multiple PROBLEM events generation". If yes probably you can disable this. Try to read documentation about this if it is your case

https://www.zabbix.com/documentation/2.4/manual/config/triggers/trigger

OK. What is the Interval on the item with vfs.fs.size[{#FSNAME},pfree] ?

Multiple PROBLEM events generation is Already Disabled

Its Update interval is 600s , I did chage this from 3600s to 600s but the issue exists with both

[kloczek]

Multiple PROBLEM events generation is Already Disabled

Its Update interval is 600s , I did chage this from 3600s to 600s but the issue exists with both

Go to dashboard-> click on Name column on your trigger and check:
- Configuration
- History and switch from Graph view to Values (upper right corner) and check that item used by your trigger really generates wrong or correct values.

IMO must be some kind of mistake in your item or trigger definition because triggers are very basics parts of the zabbix so by definition it is very, very low probability that something is wrong with zabbix per se.

[youngservers]

Go to dashboard-> click on Name column on your trigger and check:
- Configuration
- History and switch from Graph view to Values (upper right corner) and check that item used by your trigger really generates wrong or correct values.

IMO must be some kind of mistake in your item or trigger definition because triggers are very basics parts of the zabbix so by definition it is very, very low probability that something is wrong with zabbix per se.

Hi, Values and Graph is shows the correct data.
Here is a sample of latest values,
Timestamp Value
2015-04-15 09:20:24 5.3605
2015-04-15 09:15:04 5.3613
2015-04-15 09:14:05 5.3617
2015-04-15 09:13:05 5.3617
2015-04-15 09:12:04 5.3619
2015-04-15 09:11:04 5.3619
2015-04-15 09:10:05 5.3619
2015-04-15 09:09:05 5.3633

But the Issue is it didn't send email alerts according to these values but the very old Values.

For the Time being the temporary solution of this is I have to manually monitor through latest data or I need to recover the disk space by changing trigger parameter and then it gets latest value and after some repetition of email alerts according to action it continuous to send old values in email.

[kloczek]

But the Issue is it didn't send email alerts according to these values but the very old Values.

So only point where something is wrong is your trigger definition. According to previous mail it is:

{File-server:vfs.fs.size[{#FSNAME},pfree].last(0)}<7}

Is this "File-server" it is the the same host name where you have monitoring data with about 5% free space?