triggers not fired

[felixn]

hmm they seem slowly to change to OK, but why does it take so long for it all to respond?

[aib]

I'm not sure about macros {#FSNAME}
Could you check that Last Data you are getting from

key: vfs.fs.size[{#FSNAME},pfree]

OR from key

vfs.fs.size[[B]C:[/B],pfree]

[felixn]

Sorry I am not sure what you want me to do?

F

[aib]

There is my Latest Data
Notice that my key is vfs.fs.siz[C:,pfree]
After the discovering process done, the real host has the real items with real name of drive.

When you create Template (Items/Triggers/LLD), you can use macros {#FSNAME}.
When you monitor the real host - you have to use the real name.

Do yo understand my bad English?

[felixn]

I am using templates and is what it looks like - the whole thing started with how I could override default thresholds on different hosts.

So I changed the expression/condition to a MACRO and the overriding the MACRO value on the given host.

And while testing things was acting weird, and I just dont get it takes so long for the changes to kick in.

Is there another way to override default thresholds on given hosts/triggers

Felix

[aib]

Now I would ask you to change the trigger expression for the host to

{cphxxxx:vfs.fs.size[C:,pfree].last(0)}<5

It make the life easier.

[felixn]

I see now that the filesystem discovery is "Mounted filesystem discovery" is 3600 sec. so it would take a hour for it to update or?

item "Free disk space on {#FSNAME} (percentage)" is 60 sec.

so after the first 3600 it will trigger after each 60 sec.?

Let me try and change it again and use the macro value - and change 3600 to 120 or something.

But let me try your suggestion first

[felixn]

so you want me to try and disable the discovery item/trigger and make my own right?

because when I check the triggers the discovery made it correctly

{cphxxxx:vfs.fs.size[{#FSNAME},pfree].last(0)}<5

[aib]

3600 for LLD means that "Try to discovery all Filesystem every hour. If somebody changed settings for Trigger Prototype/Item Prototype - update it by creating a new Item/Trigger and deleting old stuff"

[felixn]

I think I understand a little more...

the discovery rules like Mounted filesystem discovery will update(generate the actual triggers after the update time - default 3600), so it takes an hours before the triggers has been populated.

using macros seems to work, but is not the best way to do it, because I would probably need to override the drive it self and the threshold based on a given host.

So I need to disable the present discovery rule and make my own with static values - make sense?

[felixn]

Hi

I don't get it, I have another host now that just will not trigger. When I look at the triggers (generated from the discovery) it looks just right and latest data reports a number much lower.

last data:

Free disk space on /data/p4depots/prj_pro (percentage)
vfs.fs.size[/data/p4depots/prj_pro,pfree]
60
7
365
Zabbix agent
02 May 2014 23:36:44
14.3% (free percent)


trigger:
Mounted filesystem discovery: Free disk space is less than 20% on volume /data/p4depots/prj_pro {cphyyyy:vfs.fs.size[/data/p4depots/prj_pro,pfree].last(0)}<20


I am getting crazy here

[felixn]

If I disable the trigger and create a new one with the same expression - it works

Any suggestions?

[felixn]

Hi again,

Well this just don't work proper - I have lots of latest data matching a trigger rule, and it don't trigger

Thanks