This is the documentation page for an unsupported version of Zabbix.
Is this not what you were looking for? Switch to the current version or choose one from the drop-down menu.

11 What's new in Zabbix 2.0.6

11.1 New notification macros

  • Macros {TRIGGER.TEMPLATE.NAME} and {TRIGGER.HOSTGROUP.NAME} will return the list of templates and host groups, respectively, in which the trigger is defined.
  • Macros {TRIGGER.NAME.ORIG}, {ITEM.NAME.ORIG} and {ITEM.KEY.ORIG} will return the original name/key with macros not expanded.

See macros supported by location for details.

11.2 Frontend improvements

11.2.1 New translations

  • Lithuanian

11.2.2 Completed translations

The following translations are 100% completed for this release:

  • American English
  • Brazilian Portuguese
  • French
  • German
  • Greek
  • Japanese
  • Russian
  • Slovak
  • Ukrainian

11.2.3 Updated translations

  • American English
  • Brazilian Portuguese
  • Dutch
  • French
  • German
  • Greek
  • Hungarian
  • Japanese
  • Latvian
  • Russian
  • Slovak
  • Spanish
  • Turkish
  • Ukrainian

11.2.4 Miscellaneous frontend improvements

  • Dashboard performance was improved by reducing the amount of SQL statements.
  • Action conditions with deleted objects are handled differently. Starting with Zabbix 2.0.6 if any object (host, template, trigger, etc) that is used in the action condition is deleted, the condition is deleted and the action is disabled to avoid incorrect execution of the action. Before 2.0.6 the missing object was displayed as unknown and the condition remained in place.
  • The value part of an action condition is now displayed in italics to make action conditions easier to read; like this: Host=New host

11.3 Daemon improvements

11.3.1 Improved LLD performance

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:

  • Already discovered items will be updated only if some of their properties have changed.
  • Only changed fields will be updated.
  • The amount and size of the SQL statements has been reduced.
  • Field validation LLD macro resolution has been improved:
    • validity of UTF-8 sequences
    • validity of field length

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.

11.3.2 Miscellaneous daemon improvements

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 [] started to fail ([connect] cannot connect to [[]:10051]: [111] Connection refused)
       active check configuration update from [] started to fail (cannot connect to [[]:10051]: [111] Connection refused)

and when it is restored later:

active check data upload to [] is working again
       active check configuration update from [] is working again