Alert after 5 minutes

[unizabbix]

Hi, I've a trigger that runs when Memory Usage is greater than 75% or 90%.
Trigger expression is :
{my.template:system.mem.min(300)}>my.template:vm.m emory.size[total].min(300)}*0.75

where system.mem is a UserParameter that i've defined in zabbix_agentd.conf to get memory usage in byte :
UserParameter=system.mem,free -bt | grep Mem | tr -s [:space:] | cut -d ' ' -f 3

My trigger should bu run when memory usage (> 75% of Total Memory) persists after 5 minutes. I think my expression is correct, but I receive alert just when memory go up max value setted.

Where I go wrong?


P.S. Excuse me for my english!!!

[bondbig]

Try this:
{my.template:system.mem.avg(300)}>my.template:vm.m emory.size[total].avg(300)}*0.75

But i may be wrong.

[unizabbix]

Try this:
{my.template:system.mem.avg(300)}>my.template:vm.m emory.size[total].avg(300)}*0.75

But i may be wrong.

Doesn't work yet.

[unizabbix]

Can anybody help me?.... maybe there is another way to do that....

[tighep]

How is the item set up? Also, can you post the values you see when you are getting the alert?

[unizabbix]

I've two items : one for total memory, configured in Template_Linux (vm.memory.size[total]) and the other one is system.mem that i've configured by User Parameter, as displayed above.

I don't understand the second question, I receive alert (by email) just when trigger status became TRUE and not after 5 minutes.

[tighep]

I setup almost the exact scenario as you, but my trigger fired as expected, after 5 minutes of high memory usage. How often are you running these checks?

[unizabbix]

30 second for used memory and 1800 for total memory.
Is there something wrong in update interval?

[nelsonab]

I'm really starting to wonder if this is a bug. I've seen a similar problem for years, but I never dove deep enough into it to see if it was a screwup on my part or a bug. I'll go digging around some more this evening on my end.

[unizabbix]

I've noticed that if memory is lower 75% and goes up, I receive alert after five minutes, how it should be, but during the time when memory is upper 75%, if memory goes down for few minutes (< 5) and returns at the previous value (> 75%), I receive alert immediately and not after five minutes.
Is this a bug??