These notes are for upgrading from Zabbix 5.4.x to Zabbix 6.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 6.0.0 from versions before Zabbix 5.4.0. See the upgrade procedure section for all relevant information about upgrading from previous Zabbix versions.
To create the optimal user experience and ensure the best Zabbix performance in various production environments, the support of some older database releases has been dropped. This primarily applies to the database versions that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance.
Starting from Zabbix 6.0, the following database versions are officially supported:
By default, Zabbix server and proxy will not start if an unsupported database version is detected. It is now possible, though not recommended, to turn off DB version check by modifying AllowUnsupportedDBVersions configuration parameter for the server or proxy.
In order to improve audit logging in Zabbix and make the Audit log complete and reliable, the previously existing database structure had to be reworked. During an upgrade DB tables
auditlog_details will be replaced by the new table
auditlog with a different format. Old audit records will not be preserved.
New section Audit log has been added to the Administration→General menu allowing to enable (default) or disable audit logging. Housekeeping settings for audit, previously located under the Housekeeper menu section, have also been moved to the new Audit log section. Existing housekeeping settings will be saved.
See the list of API changes in Zabbix 6.0.0.
The functionality of simple macros has been transferred to expression macros. The existing simple macros will be converted to expression macros during the upgrade. Macros that can not be converted without exceeding the length limit will not be converted with a warning printed in the log file.
The support for positional macros in item name ($1, $2…$9), deprecated since Zabbix 4.0, has been fully removed.
The Overview section in the Monitoring menu has been removed completely. The same functionality can be still accessed by using the Data overview and Trigger overview dashboard widgets.
Each Zabbix agent 2 plugin now has a separate configuration file. By default, these files are located in the
./zabbix_agent2.d/plugins.d/ directory. The path is specified in the
Include parameter of the agent 2 configuration file and can be relative to the zabbix_agent2.conf or zabbix_agent2.win.conf file location.
Previously, spaces in user passwords have been automatically trimmed in both the User configuration form and the Login form. After the introduction of configurable password complexity requirements, spaces in passwords are no longer trimmed. So users, who thought that they had spaces in their passwords, will not be able to log in as usual and will have to enter their 'old' password without spaces. To continue using passwords with spaces, they will need to recreate their passwords.