This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:installation:upgrade_notes_440 [2019/06/14 13:51]
martins-v more precise wording
manual:installation:upgrade_notes_440 [2020/05/21 15:44] (current)
marinagen [ZBX-17767] Minimum screen width for frontend.
Line 1: Line 1:
 ==== 9 Upgrade notes for 4.4.0 ==== ==== 9 Upgrade notes for 4.4.0 ====
-​<note important>​Zabbix 4.4.0 is not released yet.</note>+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 [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions. 
 +==== Critical ==== 
 +=== Jabber, Ez Texting media types removed === 
 +Jabber and Ez Texting [[:​manual/​config/​notifications/​media|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 === 
 +[[:manual/appendix/​install/​real_time_export|Real-time export]] now also includes host names, not only the visible host names. Note that the real-time [[:​manual/​appendix/​protocols/​real_time_export|export protocol]] has been changed with host name information now an object, rather than a string/​array. 
 +=== Upgrade with MariaDB 10.2.1 and before === 
 +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 [[https://​​browse/​ZBX-17690|ZBX-17690]]). 
 +==== Informational ==== 
 +=== 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 === === Changed host export format ===
-The format of host and template export has been changed in the way how triggers are exportedPreviously all triggers were listed after the host informationNow, to achieve better readability,​ triggers that are based on one host item only in problem and recovery expression are listed within tags of the respective host item.+The format of host/template export ​in XML/​JSON ​has been changed. For more details, see [[:​manual/​introduction/​whatsnew440#​changed_host_export_format|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 [[:​manual/​introduction/​whatsnew440#​items_table_split|What'​s new in 4.4.0]]. 
 +===Zabbix frontend sets own cookie path=== 
 +If Zabbix frontend runs behind proxycookie path set by Zabbix now needs to be specified ​in the proxy configuration. See [[manual/​appendix/​other_issues#​using Zabbix frontend behind proxy|using Zabbix frontend behind proxy]] for details. 
 +=== Item update interval for unreachable hosts ===
-Note also how the expression of the triggers does not reference ​the host or item, but only the function ​(''​{last()}<>​0''​ in the example):+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 exampleif 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.
-<code xml> +=== Minimum screen width for frontend === 
-    <​hosts>​ +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
-        <​host>​ +
-            <​host>​Host</​host>​ +
-            ​... +
-            <​items>​ +
-                <​item>​ +
-                    <​name>​Item</​name>​ +
-                    <​type>​0</​type>​ +
-                    <​snmp_community/>​ +
-                    <​snmp_oid/>​ +
-                    <​key>​item.key</​key>​ +
-                    ... +
-                    <​triggers>​ +
-                        <​trigger>​ +
-                            <​expression>​{last()}<>​0</​expression>​ +
-                            <​recovery_mode>​0</​recovery_mode>​ +
-                            <​recovery_expression/>​ +
-                            <​name>​Item value not 0</​name>​ +
-                            <​correlation_mode>​0</​correlation_mode>​ +
-                            <​correlation_tag/>​ +
-                            <​url/>​ +
-                            <​status>​0</​status>​ +
-                            <​priority>​2</​priority>​ +
-                            <​description/>​ +
-                            <​type>​0</​type>​ +
-                            <​manual_close>​0</​manual_close>​ +
-                            <​dependencies/>​ +
-                            <​tags/>​ +
-                        </​trigger>​ +
-                    </​triggers>​ +
-                </​item>​ +
-            </​items>​ +
-        </​host>​ +
-    </​hosts>​ +
-However, triggers that are more complex and contain several host items are listed within separate <​triggers>​ tags, as before.