manual:installation:upgrade_notes_400

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
Next revision Both sides next revision
manual:installation:upgrade_notes_400 [2017/02/16 10:09]
manual:installation:upgrade_notes_400 [2017/12/14 08:16]
martins-v not sure if value cache impact is still valid
Line 1: Line 1:
 +==== 10 Upgrade notes for 4.0.0 ====
 +
 +<note important>​Zabbix 4.0.0 is not released yet.</​note>​
 +
 +These notes are for upgrading from Zabbix 3.4.x to Zabbix 4.0.0.
 +
 +It is possible to upgrade to Zabbix 4.0.0 from versions before Zabbix 3.4.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions.
 +
 +=== Server parameter for passive proxies mandatory ===
 +
 +The Server parameter in passive proxy [[:​manual/​appendix/​config/​zabbix_proxy|configuration]],​ which previously was ignored, is now mandatory. The passive proxy will reject an address that is not listed in the Server parameter.
 +
 +=== Improved database down messages ===
 +
 +Database down messages have been improved to provide more details about the occurred problem. ​
 +Database down message from now on consists of the following content: ​
 +  [MySQL|PostgreSQL|Oracle|IBM DB2] database <DB Name> on <DB Host>​[:<​DB Port>] is not available: <error message depending on the type of DBMS (database)> ​
 +<DB Port> ​ is added to the message only if it is not the default value (not “0”).
 +
 +=== Problem name generation ===  
 +  
 +Problem and event names are now [[:​manual/​introduction/​whatsnew400#​problem_name_generation|stored directly]] in the event and problem tables upon event generation, instead of being generated in runtime as previously. A database patch will populate the new problem name and event name fields without macros expanded. ​  
 +
 +<note warning>​Database upgrade during the initial server startup may take a long time if there are a lot of old events and {ITEM.VALUE},​ {ITEM.LASTVALUE} macros are used in trigger names.</​note>​
 +
 +The default values for the new event and problem name fields are:  
 +  * For trigger events - trigger name with all the macros resolved  ​
 +  * For internal events -  
 +    * //Cannot obtain item value// - for unsupported items  ​
 +    * //Cannot calculate trigger expression//​​ - for unknown triggers  ​
 +  
 +== Related macro changes ==  
 +  
 +Related to this development there are several changes in macros:​  ​
 +  * A new {EVENT.NAME} macro is supported, returning the event/​​problem name with macros resolved.  ​
 +  * {TRIGGER.NAME} has been replaced by {EVENT.NAME} in all default messages.  ​
 +  * {TRIGGER.NAME} is replaced by {EVENT.NAME} in all trigger-based actions when upgrading.  ​
 +  
 +== Related API changes ==  
 +  
 +''​​problem.get''​​ and ''​​event.get''​​ methods have been changed in such a way that input parameter search/​​filter with object {'​​name':​​ '​​...'​​} as value is used to find matching results (by field "​​name"​​) in the corresponding table ("​​problem"​​ or "​​events"​​).  ​
 +  
 +''​​problem.get''​​ and ''​​event.get''​​ methods have been extended by adding a response parameter called "​​name"​​. For both methods, the new parameter contains a value from the newly added "​​name"​​ field in the database table "​​problem"​​ or "​​events"​​.
 +