Delayed trigger

[rsokoll]

Hi,

I want to get notified only if a value stays for at least 10 Minutes over a defined level:

{router.remoteoffice.example.com:net.if.out[tun0].min(600)}>0.1M or {router.remoteoffice.example.com:n[URL="http://et.if.in/"]et.if.in[/URL][tun0].min(600)}>0.1M

But the trigger fires immediately.
By reading https://www.zabbix.com/documentation...gers/functions I would expect that the trigger fires after 10 Minutes?

What am I missing?
(Zabbix 3.4)

[kernbug]

Hi,

I want to get notified only if a value stays for at least 10 Minutes over a defined level:

{router.remoteoffice.example.com:net.if.out[tun0].min(600)}>0.1M or {router.remoteoffice.example.com:n[URL="http://et.if.in/"]et.if.in[/URL][tun0].min(600)}>0.1M

But the trigger fires immediately.
By reading https://www.zabbix.com/documentation...gers/functions I would expect that the trigger fires after 10 Minutes?

What am I missing?
(Zabbix 3.4)

Hello

Please, show latest data for:
router.remoteoffice.example.com:net.if.in[tun0]

router.remoteoffice.example.com:net.if.out[tun0]

[Linwood]

One problem could be a startup on. If you have no data for 10 minutes (newly discovered item, new host), then the first data item meets that criteria, it will fire. You could do a count test to make sure there's enough data for the min to be meaningful.

[kloczek]

https://www.zabbix.com/documentation/3.4/manual/config/triggers/expression#hysteresis

[rsokoll]

Hello

Please, show latest data for:
router.remoteoffice.example.com:net.if.in[tun0]

router.remoteoffice.example.com:net.if.out[tun0]

router:~ # zabbix-agentd -t net.if.in[tun0]
net.if.in[tun0]                               [u|124455731947]
router:~ #

router:~ # zabbix-agentd -t net.if.out[tun0]
net.if.out[tun0]                              [u|34026575514]
router:~ #

So I do have data.
Also I see data in Monitoring -> latest data.

[rsokoll]

A note: The agentd is 2.2.21, while the server is 3.4 - but that should not cause problems, I hope?

[kloczek]

A note: The agentd is 2.2.21, while the server is 3.4 - but that should not cause problems, I hope?

Dosn't matter.
In zabbix stack triggers are always and only evaluated on the server.

[rsokoll]

I'm an idiot.
There is no problem and there never was. I'm testing the wrong way.
I wrongly assumed that after storing the trigger, it will evaluate the next 600 seconds. But it evaluates the past 600 seconds, and the values are above 0.1M, so the trigger fires immediately.

Sorry for the noise.