These notes are for upgrading from Zabbix 4.4.x to Zabbix 5.0.0. All notes are grouped into:
Critical- the most critical information related to the upgrade process and the changes in Zabbix functionality
Informational- all remaining information describing the changes in Zabbix functionality
It is possible to upgrade to Zabbix 5.0.0 from versions before Zabbix 4.4.0. See the upgrade procedure section for all relevant information about upgrading from previous Zabbix versions.
The minimum required PHP version has been upped to 7.2.0 from 5.4.0.
This change also affects the ability to install Zabbix frontend from packages in some distributions. See detailed instructions for installing Zabbix frontend from packages on RHEL/CentOS 7 and the affected Debian/Ubuntu versions.
The IBM DB2 database is no longer supported by Zabbix.uu
Microsoft Internet Explorer 11 is no longer supported by Zabbix.
mbedTLS (PolarSSL) crypto library is no longer supported by Zabbix. Supported crypto libraries are GnuTLS and OpenSSL.
Minimum database versions required for Zabbix 5.0.0 have been upped to:
Support for binary64 floating point values has been added in new installations. However, when upgrading existing installations the database tables are not upgraded automatically and a warning about this is logged during startup. Optional database patches have been made available for manually changing all fields to double precision:
To upgrade the database manually, run, for example:
mysql -uzabbix -p<password> zabbix < double.sql
Note that with TimescaleDB the compression support must only be turned on after applying this patch.
The fullscreen mode has been removed from the Monitoring sections of the frontend. The same effect (showing only page title and content) now can be achieved by hiding the new vertical menu. The kiosk mode (page content only, no page title at all) remains.
The EnableRemoteCommands parameter is now deprecated. Remote commands are still disabled by default, but in the new configuration files that is expressed by using the new DenyKey parameter (
DenyKey=system.run[*]). Remote commands can be enabled by removing (or commenting out)
The maximum allowed length of an item key has been raised from 256 to 2048 characters.
It is now possible to manually clear the SNMP cache on Zabbix server and proxy. Due to adding a new runtime control option, Net-SNMP version 5.3.0 or higher is now required for SNMP support.