These notes are for upgrading from Zabbix 4.2.x to Zabbix 4.4.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 4.4.0 from versions before Zabbix 4.2.0. See the upgrade procedure section for all relevant information about upgrading from previous Zabbix versions.
Jabber and Ez Texting media types for delivering notifications have been removed.
During the upgrade these media types, if present in your installation, will be transformed to a script media type with all relevant parameters preserved. However, notifications via Jabber and Ez Texting will not work any more.
Real-time export now also includes host names, not only the visible host names. Note that the real-time export protocol has been changed with host name information now an object, rather than a string/array.
Upgrading Zabbix may fail if database tables were created with MariaDB 10.2.1 and before, because in those versions the default row format is compact. This can be fixed by changing the row format to dynamic (see also ZBX-17690).
Zabbix screens no longer support the possibility to display another screen as a screen element. After the upgrade, all screen cells containing another screen will be empty.
The auto-select field for selecting linked templates has been removed from host/template configuration forms. To link templates, click on Add and then select templates in the popup window.
The format of host/template export in XML/JSON has been changed. For more details, see What's new in 4.4.0.
Realtime fields have been split from the
items table into a new table called
item_rtdata. See also What's new in 4.4.0.
If Zabbix frontend runs behind proxy, cookie path set by Zabbix now needs to be specified in the proxy configuration. See using Zabbix frontend behind proxy for details.
A bug related to item check time on unreachable hosts has been fixed. This bug was introduced in Zabbix version 3.4.9 or 4.0.0. Now the item check period is recalculated based on the UnavailableDelay value, not on the item update period. This can potentially change unreachable poller performance. For example, if item previously had a delay of 1h then now it will be checked based on the UnavailableDelay value, not every 1h as it was (due to bug). Therefore it is recommended to increase UnavailableDelay value to avoid possible unreachable poller overload.
The dashboard grid in Zabbix frontend has been increased from 12 to 24 columns, therefore the minimum supported screen width has been set to 1200px.