There are some similar threads but I simply don't get this.
In my case this is not an active but passive check I even have the serveractive commented out and never use that.
All other variables from that host work fine.
Yet I get unsupported item key for some and this is not the first time I run into the issue.
I can run the get manually to query the item like:
/usr/zabbix4/bin/zabbix_get -s 1.2.3.4 -p10050 -k squid.req_fail_ratio
But always keep getting unsupported item key.
Clear history & trends does nothing, check now does nothing, trying to reenable does nothing.
Disabling reenabling the host does nothing.
Even running tcpdump on the client confirms that the variable is transmitted properly.
I have a feeling that it's cause the variable returns zero and not changing but seriously I'm clueless at this point I have spent many hours on this.
It works from the server with the get command all the time, not from the frontend.
In my case this is not an active but passive check I even have the serveractive commented out and never use that.
All other variables from that host work fine.
Yet I get unsupported item key for some and this is not the first time I run into the issue.
I can run the get manually to query the item like:
/usr/zabbix4/bin/zabbix_get -s 1.2.3.4 -p10050 -k squid.req_fail_ratio
But always keep getting unsupported item key.
Clear history & trends does nothing, check now does nothing, trying to reenable does nothing.
Disabling reenabling the host does nothing.
Even running tcpdump on the client confirms that the variable is transmitted properly.
Code:
T 10.2.0.122:60122 -> 10.2.0.111:10050 [AP] ZBXD.........squid.req_fail_ratio T 10.2.0.111:10050 -> 10.2.0.122:60122 [AP] ZBXD.........0.00
It works from the server with the get command all the time, not from the frontend.