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.

9 What's new in Zabbix 2.0.4

9.1 Frontend improvements

9.1.1 Shading of screen elements that failed to update

Since 2.0.3, screen elements are updated in background, without reloading the whole page. Zabbix 2.0.4 will darken elements that have failed to update for some reason.

9.1.2 Miscellaneous frontend improvements

  • Full cloning a template will now clone templated screens as well.
  • It is now possible to have empty recovery message body.
  • Previously, if a trigger had no events, it was shown as acknowledged in Monitoring → Triggers. Now a string No events will be shown instead.
  • Page refresh should now reload less files, thus improving overall frontend performance and decreasing the network traffic.
  • In network maps, HOST.HOST macro will now work in trigger elements.
  • Screen editing will not allow to set row or column span that would exceed row or column count.
  • In Monitoring → Overview vertically displayed text that used to be made up by images, now is actually vertical text.

9.1.3 New translations

  • Finnish
  • Indonesian
  • Persian

9.1.4 Updated translations

  • Brazilian Portuguese
  • Chinese (China)
  • Chinese (Taiwan)
  • Czech
  • French
  • German
  • Hungarian
  • Italian
  • Japanese
  • Latvian
  • Polish
  • Slovak
  • Russian
  • Ukrainian

9.2 API improvements

Method templatescreen.copy has been added.

9.3 Daemon improvements

Macro {TRIGGER.COMMENT} has been renamed to {TRIGGER.DESCRIPTION}, to match the field name. Old macro is still supported.

Default disks checked have been improved for and items when using Zabbix agent daemon with -t or -p flags. On Linux, FreeBSD, OpenBSD and Solaris disks that have higher probability of existing will be used.

Macros {HOST.HOST}, {HOST.NAME}, {HOST.IP}, {HOST.DNS} and {HOST.CONN} are now supported in the parameters field for SSH, telnet and DB monitor items.

9.3.1 Improved SNMPv3 failure handling

Previously, Zabbix server and proxy would handle all SNMPv3 querying failures as a failure of the whole host. Since 2.0.4, if SNMPv3 security name or security auth passphrase are wrong, this will be detected and such items will turn unsupported. Item information will be updated with a proper error message, which will be visible in the item configuration list.

9.3.2 Java gateway improvements

Zabbix Java gateway now supports dots in attribute name. To use such an attribute name, dots must be escaped with backslashes.