Active proxy not reporting alarm

[LdeB]

When you have an active proxy it is often like that because it sitting behind a NAT firewall of a remote site router on a live IP so you can't directly ping it etc.

So if the proxy stops, jams, crashes etc it doesn't throw up an alarm you just get a number of hours of days since the proxy was last seen on Administration->Proxies.


My problem is there a way to force an alarm when an active proxy goes missing for certain amount of time?

[cyber]

I guess you need to monitor your proxy.. There are internal items, that will help you. For example "zabbix[proxy,<name>,<param>]"

https://www.zabbix.com/documentation/current/en/manual/config/items/itemtypes/internal

[LdeB]

When I tried that it simply returns the last value of the items which is totally normal because it's the proxy that has crashed not the items.
As the proxy is active the time does not seem to matter

Using your idea what I need is something like if the last item value is more than x number of seconds ago then the proxy has crashed but I can't work out how to do that and essentially you are trying to create my next comment. Literally none of the items monitored by a missing active proxy generate any alarms at all if the proxy just crashes.

To my way of thinking an active proxy should have an alarm when not seen in a certain time ... the last time it was seen is report under administration->proxies so that would make far more sense than trying to do hijinx with items..

[cyber]

But there is suggestion for monitoring proxies availability... fuzzytime()...
Well I don't have any active proxy, so I cannot really experiment here... But for passive ones that works ...
<server>:zabbix[proxy,<proxyname>,lastaccess].fuzzytime(300)}=0 works and triggers if proxy has not been seen in 5 minutes.

[max.]

Hello,

You can add some triggers to monitor your proxy, for example status of zabbix-proxy service is up and aviability by icmp ping.
If you are concerned abount the information not beeing sent to the server it is true that as there is no data, triggers do not evaluate.

So the solution for that could be adding a trigger with the nodata function, i think it is the only one that evaluates even if the agent stops sending information.

Regards