Improved performance for event acknowledging.
Zabbix server log messages about failed checks have been improved. Previously, if a check failed, Zabbix server would log messages, similar to these:
After 3 failures like these, host would be disabled and a message logged:
If a host then became available, a log message would say:
Starting with Zabbix 1.8.9, this has been improved. First, messages now tell which specific item key failed, thus allowing to see whether the problem happens with multiple items or just one:
Additionally, for all failures item type is logged as well (in this case, Zabbix agent).
If a host is determined to be unavailable and then available, messages are a bit more verbose now and also include check type:
And a new message has been introduced if host responds after one or two failures (this was not logged before at all):
These changes should allow for much easier debugging of connectivity or configuration issues - for example, if all problems on a host would be associated with a user parameter, it would most likely be a performance problem with the executed command.
Starting with Zabbix 1.8.9 acknowledge status will be fully synchronised from child nodes to master node.
Zabbix server performance was improved in some edge cases by skipping value updating for disabled or removed items.
Starting with Zabbix 1.8.9, upon startup Zabbix daemons will wait for database to be available. This will help with case when database is started by bootup process before Zabbix daemons, but takes long time to become ready.
Zabbix agent daemon performance on AIX was improved by only collecting perfstat data if it is requested.