triggers not fired

[felixn]

Hi

I don't get it, I have modified some threshold on a discovery rule for free space percentage on filesystem.

I see latest data has data that should match the threshold, but no events or trigger beeing fired - it works on some hosts.

Anyone with some suggestions?

Thanks

[aib]

Do you mind to show us :
1) trigger construction
2) better quality of Latest Data & Event screen.

It may be as simple as small misprint.

[felixn]

sure and thanks

Trigger:
{Template OS Windows:vfs.fs.size[{#FSNAME},pfree].last(0)}>5

Item:

Zabbix agent:

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


I can't upload bigger attachments

[felixn]

Please let me know if you want more information or logs files

Thanks again
Felix

[aib]

This is my trigger Expression:

Name : Free disk space is less than 20% or 10Gb on C:
Expression: {AMD-137:vfs.fs.size[C:,pfree].last(0)}<20&{AMD-137:vfs.fs.size[C:,free].last()}<10737418240

In your case, trigger has to be like

{Template OS Windows:vfs.fs.size[{#FSNAME},pfree].last(0)}[B]<[/B]5

Because if you use symbol "Greater than 5", trigger will fired up when the free space (in percents) will be MORE than 5%.

[felixn]

Hi

This is intended I am testing the triggers together with template stuff. So I should get triggers from all my windows servers with free space greater than 5% - which should trigger all.

But the issue is that triggers are not fired.

Thanks

[aib]

Sorry for misunderstanding - but as I can see from the screenshot - triggers already fired (in state PROBLEM). When you free space will be lower than 5% - they will goes down (to OK state).

Is not a behavior which you need?

[felixn]

The text/description I have not changed, I was troubleshooting the thresholds and wanted to trigger alarms for them all there I changed the condition to something that would trigger for sure - and they don't

So I really don't understand it and must be some I did wrong, because this is basic stuff

Thanks
Felix

[aib]

well, I explained wrongly.

just for the experiment, change the expression from ">5" to "<5" and see, how your triggers will doing.

I assume that they switched back from PROBLEM to OK right after you apply the template with edited Triggers' expression.

[felixn]

I changed it to <5. lastdata has collected new values old hosts that was triggered before is still there - not ACK'ed.

What next then?

Thanks again

[felixn]

one host has reported "OK" now but only one so far

[aib]

1)I see from the first picture the Templated Trigger
Do you mind to show the real trigger, which was created after LLD?

2) How often your "Mounted Filesystem Discovery" rule repeats? Every 60 sec or every 3600 sec? New trigger will be refreshed/replaced only after repeat Discovery, you remember it?

[felixn]

default 60 sec. updates - latestdata reports values correctly each 1 minute

Free disk space on {#FSNAME} (percentage) vfs.fs.size[{#FSNAME},pfree] 60

How do I show the "real" trigger?

thx

[aib]

Configuration -> Hosts -> (select Windows Server Host) -> Triggers

On my screen I see (attached) picture, which includes Real Name (C instead of {#FSNAME} macros

[felixn]

expression =

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


latest data

02 May 2014 20:43:17 / 87.7 %

this should "OK" that host right?

Last change (last 20 issues) - cphxxxx is 12hours from last change

cphxxxx
Free disk space is less than xx% on volume C: 02 May 2014 08:45:17 12h 2s