Triggers of host monitored by proxy not working.

[RaulChiarella]

Hello!

I have hosts monitored by proxy, and i am testing a single item/trigger on them
Item is "agent.ping" and trigger is "agent.ping.nodata({$AGENT.NODATA_TIMEOUT})}=1 ", where agent.nodata_timeout is 5 minutes...

If i use this Item/Trigger on a host that isnt monitored by proxy it works just fine...
After 5 minutes of Zabbix Service not running, the trigger appears on my screen and the latest data is empty.

But if i do the same but using a PROXY that is NOT ON (I shutdown to test this) nothing happens
I checked LAST VALUE and it is empty just like when the Item is set on a host not via proxy...

Please, can someone help me?

[johndoe2374]

Hello Raul!

I think proxy have to get configuration from server first, so it can get a list of items to collect/expect from monitored hosts and then send them to server. So you can try turn it on, see if it collects data, then turn it off and check if your trigger will be calculated.

[cyber]

You have not mentioned your zabbix version, but I think it is at least 5.0?
This behaviour is expected with nodata(), it is considering the availability of proxy
Since Zabbix 5.0, the 'nodata' triggers monitored by proxy are, by default, sensitive to proxy availability - if proxy becomes unavailable, the 'nodata' triggers will not fire immediately after a restored connection, but will skip the data for the delayed period.
To turn off sensitiveness to proxy availability, use the second parameter, e.g.: nodata(5m,strict); in this case the function will work the same as before 5.0.0 and fire as soon as the evaluation period (five minutes) without data has past.

[RaulChiarella]

You have not mentioned your zabbix version, but I think it is at least 5.0?
This behaviour is expected with nodata(), it is considering the availability of proxy
Since Zabbix 5.0, the 'nodata' triggers monitored by proxy are, by default, sensitive to proxy availability - if proxy becomes unavailable, the 'nodata' triggers will not fire immediately after a restored connection, but will skip the data for the delayed period.
To turn off sensitiveness to proxy availability, use the second parameter, e.g.: nodata(5m,strict); in this case the function will work the same as before 5.0.0 and fire as soon as the evaluation period (five minutes) without data has past.

Yes, version in production is 5.4

[kaleem]

hi i unlinked the templates from hosts but still showing the triggers notification on dashboard ,how we should vanished them instead of manual unable it.