SNMP monitoring performance is significantly improved by introducing bulk requests with at most 128 items. The load on Zabbix server and monitored SNMP devices should be greatly reduced:
See more information about SNMP bulk processing.
logitems: if there is a problem with the log file (e.g. it does not exist or is not readable) the
logitem now becomes NOTSUPPORTED. Before the change (in 2.2.2) it did not go into NOTSUPPORTED state because of a bug in the agent.
logrtitem becomes NOTSUPPORTED if a directory where the log files are expected to be found does not exist.
logrtitem does not make it NOTSUPPORTED.
logrtitem are logged as warnings into Zabbix agent log file but do not make the item NOTSUPPORTED.
logrtitem became NOTSUPPORTED. Zabbix can monitor its agent log file except when DebugLevel=4.
logrtitem checks has been improved the limits on maximum number of log file records analyzed and number of matching records sent to server in one check are not modified. For example, if a
logrtitem has Update interval 1 second, by default the agent will not analyze more than 400 log file records and will not send more than 100 matching records to Zabbix server in one check. By increasing MaxLinesPerSecond parameter in agent configuration file or setting maxlines parameter in the item key the limit can be increased up to 4000 analyzed log file records and up to 1000 matching records sent to Zabbix server in one check. If the Update interval is set to 2 seconds the limits for one check would be set 2 times higher than for Update interval 1 second.