Zabbix Documentation 4.4 (current)| In development:5.2 (devel)| Unsupported:

User Tools

Site Tools



This is an old revision of the document!

9 Upgrade notes for 4.4.0

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, Ez Texting media types removed

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 protocol changed

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.


Screen element removed from screens

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.

Linked template selection

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.

Changed host export format

The format of host/template export in XML/JSON has been changed. For more details, see What's new in 4.4.0.

Items table split

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.