10 Upgrade notes for 5.4.0

Zabbix 5.4.0 is not released yet.


Supported database versions

To create the optimal user experience and ensure the best Zabbix performance in various production environments, support of some older database releases has been dropped. Additionally, an upper limit for the supported DB versions has been introduced for all databases. Though Zabbix may still work with newer releases, the maximum supported DB version indicates the latest version Zabbix has been tested with and provided stable performance.

See the list of changes in software requirements in the table below.

SoftwareBefore Zabbix 5.0Zabbix 5.0; 5.2Since Zabbix 5.4
MySQL/Percona 5.0.3 - 8.0.x 5.5.62 - 8.0.x 5.7.28 - 8.0.X
MariaDB 10.0.37 or later 10.0.37 -10.5.X
PostgreSQL8.1.X or later 9.2.24 or later 10.9.X - 13.X.X
Oracle 10g or later 11.2 or later - 19c
TimescaleDB 1.0 or later 1.0 or later 1.5 - 2.1
SQLite (proxy only) 3.3.5 or later 3.3.5 or later 3.3.5 - 3.34.X

See Software requirements page for additional information.


Host availability data

All data about host availability have been moved from the host level to the level of individual interfaces. During database upgrade all previous host availability data will be lost. New interface availability initially will be set to 'unknown' and then updated after some time.

Note that the server-proxy data exchange protocol has also been changed.

Direct connections to database removed from pollers

Calculated, aggregated and internal checks are now performed by the new history poller process. The StartHistoryPollers value should be increased if history pollers are too busy, but should be kept low if possible to avoid unnecessary connections to database.

New availability manager process has been introduced. All processes queue host availability updates to the availability manager and that queue is flushed by the availability manager to the database every 5 seconds.

You can monitor the new processes using the zabbix[process,<type>] internal item.

Naming in JavaScript objects

Naming in additional JavaScript objects has been changed.

Hidden PSK data for hosts and proxies

PSK identity and PSK fields in host and proxy configuration are now write-only. Once saved, these values cannot be viewed again in the frontend or retrieved through API but can be replaced with new values. For hosts, PSK identity and PSK will no longer be exported.

Value mapping on template/host level

As value mapping has been moved to template/host level, there is no global value mapping anymore. During the upgrade, all global value maps that are used in items will be copied to the respective template or host.

Deprecated macros

{USER.ALIAS} is now deprecated. Use the new macro {USER.USERNAME} instead.

See also: Supported macros