How to defer zabbix notification?

[Yello]

I'm not sure if the update interval value can be set online.
I have changed this value from 120 to 60 seconds without restarting zabbix server.

No need to restart server. Is your test still running? How long did it run for? The reason I say this is that you may not have given the trigger enough time to build up a history (after it was reconf'ed) and then start counting. That could take several minutes that the 4 minute data window you configured.

[mazate]

I set this trigger by cloning default template, {Template_Windows:status.last(0)}=2.
Then, I modified its expression.

About the testing scenario, I disabled network connection on client side for about 5 minutes.

Tomorrow, I will test it for 15 minutes. (today the one with the client access has already gone)

Thank you very much David, for all your help. Really appreciate it!

mazate

[mazate]

Hi David,

I've try disabling network connection for about 15 minutes, then another wired thing happened, kindly see the screen captured...

http://www.freeimagehosting.net/newuploads/f744a.png

This time no information was logged in Events tab.

Thank you,
mazate

[Yello]

Hi,
Ok, I now think I realise what's going on. You don't provide enough information to be certain but when I explain I expect you'll go away and do some work to make things better I expect.

The item you're tracking to determine if the host is down is an agent status item. It is intended to tell you whether the agent is responding or not. I usually disable the agent status item and triggers because problems can sometimes occur (if I recall). I suggest you search the forum and you'll find discussion on it.

However, if you think about it, when you pull the ethernet cable this trigger cannot fire. Because it is an agent to server status check no data will be passed over the wire, unless you have a specific management network. In situations where you want to trigger when no data is received use the "nodata" trigger function.

Putting all of that to one side, I would suggest implement some simple checks to ping network interfaces and ports on the monitored server. That way you can determine whether the host is up or down regardless of the state of the agent. Using the agent status item as a proxy for host status is specious IMHO.

Regards,
David

[mazate]

Hi David,

Thank you very much for all your suggestions.
The reason that I am using "status" key is that it is bundled within the default Windows template.
I will try to go with a simple check, ping... perhaps.

BR,
mazate

[mazate]

Now I'm using icmpping with this expression,
{Template_Windows:icmpping.count(300,0,"eq")}>3
and it's working fine.

Thanks again for all your help,
mazate