How to monitor missing SNMP data collected by proxy

[Baymon]

Hi,

i have this topology:

Zabbix Server <-- Zabbix active Proxy --> SNMP Device

The Proxy polls items from the server, collects the data with SNMP and sends data back to the server.

Now i had the problem that after updates of the infrastructure Server and one Proxy had different versions for some time, Server 6.2.0, Proxy 6.0.0

In result the server could not parse the data delivered by the proxy and no items were updated with new values, but also no triggers were fired. There was no alert at all about the broken connection between server and proxy.

1321:20230227:232448.725 proxy "zabbix-proxy-host" protocol version 6.0 differs from server version 6.2
1. Failed: cannot extract value from json by path "$.ServerUptimeSeconds": no data matches the specified path

How do i monitor missing item values in this case?

Normaly i do that with an internal item

key: zabbix[queue,10m]
trigger: min(/zabbix-host/zabbix[queue,10m],10m)>50

But for this proxy topology this does not work.

Thanks a lot for help.

[Atsushi]

If Zabbix server version is 6.2, Zabbix proxy version should also be 6.2.

[Baymon]

Sure, but we missed the update with one proxy. A monitoring system should trigger an alert if no data is received anymore. What will be the right item and trigger to monitor such case? I spend hours with testing and reading documentation but i couldn't find a solution for this.

[Baymon]

Nobody an idea how to monitor missing SNMP data collected by a proxy?

[cyber]

Make sure you dont miss upgrades..

Following are from current LTS version...

https://www.zabbix.com/documentation/6.0/en/manual/installation/upgrade/packages/debian_ubuntu

While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the same major version. Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded

https://www.zabbix.com/documentation/6.0/en/manual/appendix/compatibility

It is no longer possible to start the upgraded server and have older and unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxie

6.4 came just out. they have improved this scenario there... you can have mismatched proxy versions now. Until now it was pretty much requirement...

[Baymon]

Sure, updates are always important and all components should have the same version. However, beside incompatibility there can be other reasons why snmp monitoring in the described scenario fails for example network issues in between. How can i make sure and monitor that snmp data is sent within a defined time interval and how can i trigger an alarm if data is not received as expected?

[cyber]

Internal items.

zabbix[proxy,<name>,<param>]
	Information about Zabbix proxy.			Integer.	name: proxy name Valid values for param are: lastaccess - timestamp of last heart beat message received from proxy delay - how long collected values are unsent, calculated as "proxy delay" (difference between the current proxy time and the timestamp of the oldest unsent value on proxy) + ("current server time" - "proxy lastaccess") Example: => zabbix[proxy,"Germany",lastaccess] fuzzytime() function can be used to check availability of proxies. This item is always processed by Zabbix server regardless of host location (on server or proxy).