. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 7 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773 Appendix 2. Changes from 2.0 to 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 Zabbix API changes in 2.2 . . . . . . . . . . . . . . items have gained the optional

parameter: log[], logrt[] and web.page.regexp[]. Related changes: • if no match for the regular expression is found, an empty string is returned (instead of EOF)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 8 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187 Appendix 2. Changes from 3.4 to 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192 Zabbix API changes in 4.0 . . . . . . . . . . . . . long, so in real life situations there may be a need to retrieve a new value quicker - to pick up changes in discoverable resources, for example. This is now made possible in the new Zabbix version by means

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 9 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954 Appendix 2. Changes from 2.4 to 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959 Zabbix API changes in 3.0 . . . . . . . . . . . . . . with a completely new frontend design. Along with visual improvements, there are several other changes for working with the frontend: • For accessing the second-level menu, top level options (Monitoring

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 9 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996 Appendix 2. Changes from 3.2 to 3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998 Zabbix API changes in 3.4 . . . . . . . . . . . . . . parameter. Alerts generated by one trigger are processed sequentially. There are other related changes: • Three new alert processing options available in the media type configuration: Concurrent sessions

Zabbix 1.4.x and Zabbix 1.6.x can be used with Zabbix 1.8. It does not require any configuration changes on agent side. Warning: Older Zabbix proxies of version 1.6.x can’t be used with Zabbix 1.8, they version 1.8.20 If Zabbix is logging to syslog then after an upgrade to Zabbix 1.8.20 you will see changes in the application names appearing in syslog: Zabbix Agent → zabbix_agent Zabbix Agent → zabbix_agentd monitoring of syslog you may want to adjust them for the new application names. 3.4 System requirement changes Additional or increased system requirements: • Support for PHP 4 dropped. • Maximal PHP memory

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 9 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421 Appendix 2. Changes from 5.4 to 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426 Zabbix API changes in 6.0 . . . . . . . . . . . . . design it is possible to create a very flexible setup. 5 What’s new in Zabbix 6.0.0 See breaking changes for this version. High availability cluster for Zabbix server The new version comes with a native

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 9 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539 Appendix 2. Changes from 5.2 to 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544 Zabbix API changes in 5.4 . . . . . . . . . . . . . triggers/calculated items aimed at resolving the known limitations of the former syntax. The major changes and advantages coming with the new syntax are as follows: • A unified syntax can be used in trigger

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 7 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775 Appendix 2. Changes from 2.2 to 2.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777 Zabbix API changes in 2.4 . . . . . . . . . . . . . . sorted by two new columns added to the list - Active since and Active till: 17 5.10.11 Host menu changes Linking to graphs The host menu has gained a new entry for quickly accessing host graphs. Unavailable

selection elements are now highlighted with a thick rectangular border. ** Element properties window changes ** Map element properties window has received multiple modifications. • Links are only shown when unsupported item, and ignored for other item types by the Zabbix server. 5.3.2.4 External check parameter changes External check parameter handling was changed. Previously, only one parameter was accepted. Starting unknown status. This status will only be used for informational purposes. 5.5.6 Supported macro changes 5.5.6.1 Common macros In interface IP and DNS fields the following macros are supported: • {HOST

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 9 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888 Appendix 2. Changes from 3.0 to 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890 Zabbix API changes in 3.2 . . . . . . . . . . . . . . Polish • Portuguese (Brazil) • Russian • Slovak • Spanish • Turkish • Ukrainian 5.14 Daemon changes/improvements 5.14.1 Host availability, discovery, auto-registration and history data validation