Notes 3.1 Installation See the installation_from_source section for full details. 3.2 Version compatibility Older agents from Zabbix 1.0, Zabbix 1.1.x, Zabbix 1.4.x and Zabbix 1.6.x can be used with Zabbix MySQL alter table dhosts drop index dhosts_1; alter table dservices drop index dservices_1; alter table httptest drop index httptest_2; alter table httptest drop index httptest_3; alter table history_log index history_log_2; alter table history_text drop index history_text_2; alter table actions drop index actions_1; alter table escalations drop index escalations_2; alter table graphs_items drop index graphs_items_1;

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120 13 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . server will also accept historical data from 3.2 (and older) proxies, keeping partial backwards compatibility. • The default data storage period for internal, discovery and agent auto-registration events using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 11 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frontend improvements 5.2.1 A new look Zabbix frontend has received a redesign. The login page, table view, configuration wizard, default trigger severity colours all have a fresh new look. 5.2.2 Reworked and graph sections was improved. • All frontend problems visible in Internet Explorer with ”Compatibility mode” enabled have been solved 8.1.7 New translations • American English • Chinese (Taiwan)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255 13 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the ”data” element has been removed from all native items related to discovery, for backward compatibility Zabbix will still accept the JSON notation with a ”data” element, though its use is discouraged {HOST.HOST}, {HOST.ID},{HOST.IP},{HOST.NAME}, {INVENTORY.*} macros {MAP.NAME} Note that this table lists only the new locations. So, even though {HOST.ID}, {HOSTGROUP.ID}, {TRIGGER.ID} and {MAP.ID}

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351 11 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the severity of the underlying trigger and could not be changed. Now problem severity in the event table is a separate field and can be updated. Even though the original value is based on the trigger severity severity active blocks are now styled in severity colors while inactive blocks have the same color as table background color. This change applies to the ”Media” tab in Administration → Users → User properties

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059 12 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . for entities with no items. Whereas previously a (0) would be displayed next to the entity in a table column, now nothing is displayed. Previous version: 19 Zabbix 3.0: 5.19.6 User agent options issues” and ”Host group issues” screen elements now display all hosts from trigger expression. • A table header has been added to the user media listing. Entries from the list can be deleted using the Remove

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 12 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . corresponding history tables. Those fields were redundant and removing them will simplify history table structures and will remove unnecessary overhead when inserting values. See also • Template changes statistics on Windows. 7.5.3 Chassis information Changed system.hw.chassis key to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory. 7.6 Trigger functions •

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906 12 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the recommended course of action if housekeeping encountered problems with, say, a large history table. That, however, also meant disabling all housekeeping tasks, while the real problem was only with with internal items. 5.25.5 Reducing update operations in item table Previously Zabbix would update several fields in the ’items’ table for each new value, resulting in a large number of SQL update operations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898 11 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . list, Status column has been moved to the end • The value of Max count of elements to show inside table cell from Administration → General → GUI now also applies to templates listed in the host list, users using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1848 11 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . passive agent checks A JSON-based protocol for passive agent checks has been implemented. For compatibility with older agents, a failover to the old plaintext protocol has been added. If the agent returns group sets and host group sets for each user/host respectively. Additionally, there is a permission table storing only the accessible combinations of users and hosts, specified by the hash IDs. This improvement