See macros supported by location for details.
The following translations are 100% completed for this release:
Previously, low level discovery could generate a large amount of database queries, and even result in deadlocks. Starting with Zabbix 2.0.6, each low-level discovery prototype will be processed in its own transaction, avoiding the deadlocks.
Item prototype processing has also been significantly improved:
In a test run, the amount of SQL queries in the initial LLD run was reduced 64 times. In further runs when there are no changes to the discovered entities the amount of SQL queries was reduced 250 times. In further runs when there were changes the amount of SQL queries was reduced 210 times. Note that the total size of SQL queries was reduced even more.
The amount of traffic that is exchanged between Zabbix server and Java gateway was reduced.
The Zabbix server escalator process generates alerts while processing escalations. Previously these alerts were not available to the alerter process immediately, but only after the escalator finished its job. This has been fixed by splitting one transaction to handle all escalations into a separate transaction for each, which results in alerts becoming available to the alerter while the escalator is busy.
Logging failed active check connection
Zabbix agent now generates log warnings when an active check connection to server/proxy fails:
active check data upload to [127.0.0.1:10051] started to fail ([connect] cannot connect to [[127.0.0.1]:10051]:  Connection refused) active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]:  Connection refused)
and when it is restored later:
active check data upload to [127.0.0.1:10051] is working again active check configuration update from [127.0.0.1:10051] is working again