Type: Problem report
Status: Need info
Affects Version/s: 5.2.4
Fix Version/s: None
Component/s: Server (S)
Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-65-generic x86_64)
DB (separate host):
PostgreSQL 11.3 (Ubuntu 11.3-1.pgdg16.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609, 64-bit
An SNMP low-level discovery rule that fails appears to block data collection of other unrelated SNMP data items, and also keeps trying to discover, ignoring the configured discovery interval.
Based on the logs, it appears that a non-existent OID error is treated the same as a timeout error.
Verifying that these two conditions are in fact distinguishable:
The attached graph of several unrelated items did not have gaps in it before adding the discovery rule.
These log entries continue every 1 to 2 minutes or so.
I disabled the discovery rule at approximately 1154, and no log entries appear after that time:
I would suggest that Zabbix not treat "no such object" the same as "timeout" (if this is in fact the case, as the log seems to imply) in either LLD, or in regular data collection; and that an LLD OID that doesn't exist should just mean that the item(s) is not discovered (or lost) until the next time the LLD rule should run. And a regular item OID that doesn't exist should not stop or suspend collection of other items (but should log/report as appropriate).