min(600) trigger firing too soon

[dreas]

We are monitoring our SMTP server with two triggers.

Trigger 1: server1:net.tcp.service[smtp].last(0)=0
Trigger 2: server1:net.tcp.service[smtp].min(600)=0
Item: net.tcp.service[smtp] every 60 seconds.

Trigger 1 sends an email and trigger 2 sends a SMS. It happens however that trigger 2 gets triggered at the same time as trigger 1. So there has not been a problem for 600 seconds at that moment yet.

Running ZABBIX 1.4.1

[Alexei]

We are monitoring our SMTP server with two triggers.

Trigger 1: server1:net.tcp.service[smtp].last(0)=0
Trigger 2: server1:net.tcp.service[smtp].min(600)=0
Item: net.tcp.service[smtp] every 60 seconds.

Trigger 1 sends an email and trigger 2 sends a SMS. It happens however that trigger 2 gets triggered at the same time as trigger 1. So there has not been a problem for 600 seconds at that moment yet.

Running ZABBIX 1.4.1

Everything is absolutely correct and works as expected! You may want to redefine your second trigger to server1:net.tcp.service[smtp].max(600)=0.

[dreas]

Pff. You are absolutely right. Sorry about that.