can I build a delay in the initial action?

[acidzebra]

I have a zabbix box monitoring some 20 servers across Europe. I am using the default win32 template on all hosts with some minor modifications.

Unfortunately, some of our remote offices are on flakey lines and will sometimes experience a small 40-second (or so) 'hiccup'.

At which point Zabbix triggers (host unreachable) and an action is executed (mail is sent out).

I would like to have some delay, i.e. when the host remains unreachable for, say, two minutes THEN send out the mails.

Is this possible?

[den_crane]

...
Is this possible?

In trigger u see expression {Windows_t:status.last(0)}=2 ? It means that if last value equals 2 trigger is on.
Change expression {Windows_t:status.min(120)}=2 -- It means that last 120 seconds min value = 2 (all 120 sec host was unreachable)

[peter_field]

See http://www.zabbix.com/forum/showthread.php?t=4043 for another example of this.

[bashman]

I have a zabbix box monitoring some 20 servers across Europe. I am using the default win32 template on all hosts with some minor modifications.

Unfortunately, some of our remote offices are on flakey lines and will sometimes experience a small 40-second (or so) 'hiccup'.

At which point Zabbix triggers (host unreachable) and an action is executed (mail is sent out).

I would like to have some delay, i.e. when the host remains unreachable for, say, two minutes THEN send out the mails.

Is this possible?

I think you can use escalations, I understand that escalations check if the trigger is still true (PROBLEM) in each step, so If triggers becomes false (OK) before the delay time (before the step that runs the remote command) the action will be aborted and no command will be executed.

Another option is to modify Server configuration file, parameter SenderFrequency, but all the actions will be affected.