Zabbix Documentation 3.2

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:installation:upgrade_notes_320

Differences

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_320 [2016/11/23 09:41]
martins-v adding introductory notes and linking to upgrade procedure page; removing auto numbering
manual:installation:upgrade_notes_320 [2019/02/12 06:39]
martins-v formatting change
Line 1: Line 1:
-==== Upgrade notes for 3.2.0 ====+==== 10 Upgrade notes for 3.2.0 ====
  
-These notes are for upgrading from Zabbix 3.0.x to Zabbix 3.2.0.+These notes are for upgrading from Zabbix 3.0.x to Zabbix 3.2.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 3.2.0 from versions before Zabbix 3.0.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions. It is possible to upgrade to Zabbix 3.2.0 from versions before Zabbix 3.0.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions.
  
-=== Delaying escalations during maintenance ​===+==== Critical ==== 
 + 
 +=== Database upgrade === 
 + 
 +The history_text.id and history_log.id fields will be removed from the corresponding history tables during database upgrade. Depending on the history table size this process can be slow. 
 + 
 +=== Case-sensitive MySQL database === 
 + 
 +A case-sensitive MySQL database is required for proper server work. It is [[:​manual/​appendix/​install/​db_scripts#​mysql|recommended]] to create a case-sensitive MySQL database during new installations. If you created a MySQL database with the utf8 character set previously, in order to support case sensitiveness of stored data, you need to convert the charset to utf8_bin. 
 + 
 +==== Informational ==== 
 + 
 +=== Escalation changes === 
 + 
 +== Delaying escalations during maintenance ==
  
-The logic of delaying problem notifications during host maintenance has been changed. ​+The logic of delaying problem notifications during host maintenance ​[[:​manual/​introduction/​whatsnew320#​delaying_escalations_during_maintenance|has been changed]]
  
-In previous Zabbix versions, problem notifications during a host maintenance period were "​suppressed" ​if you were using the //​Maintenance status = not in "​maintenance"//​ action condition. In the new version, the old mechanism is dropped. Instead there is an new //Pause operations while in maintenance//​ option in action configuration,​ which allows to pause notifications ​in the host maintenance ​phase if you wish so. +In previous Zabbix versions, problem notifications during a host maintenance period were skipped ​if you were using the //​Maintenance status = not in "​maintenance"//​ action condition. In the new version, the old mechanism is dropped. Instead there is new //Pause operations while in maintenance//​ option in action configuration,​ which allows to pause notifications ​during a maintenance if you wish so. 
  
 To ensure that escalations using this functionality work properly after the upgrade you must reconfigure the relevant actions by: To ensure that escalations using this functionality work properly after the upgrade you must reconfigure the relevant actions by:
Line 15: Line 32:
   * removing the //​Maintenance status = not in "​maintenance"//​ condition   * removing the //​Maintenance status = not in "​maintenance"//​ condition
   * making sure that //Pause operations while in maintenance//​ is selected in action configuration   * making sure that //Pause operations while in maintenance//​ is selected in action configuration
 +
 +== Parallel escalation for each of multiple PROBLEM events ==
 +
 +Before Zabbix 3.2 every new //PROBLEM// event would abort the escalation of an earlier //PROBLEM// event, i.e. only one active escalation could run for a trigger with multiple event generation. Now escalation procedures for all these events are processed in parallel. This change and newly introduced [[manual/​config/​event_correlation|event correlation]] and [[manual/​config/​triggers/​event_tags|event tags]] enable more flexible approach to multiple //PROBLEM// event resolution. For example, depending on configuration now //OK// event may either stop escalation for the particular //PROBLEM// event, for numerous events or for all of them. 
 +
  
 === Recovery operations === === Recovery operations ===
Line 36: Line 58:
  
 Recovery operations also get a dedicated tab in the action configuration form, while the condition tab has been dropped and conditions now can be set in the general action property tab. Recovery operations also get a dedicated tab in the action configuration form, while the condition tab has been dropped and conditions now can be set in the general action property tab.
- 
-=== Database upgrade === 
- 
-The history_text.id and history_log.id fields will be removed from the corresponding history tables during database upgrade. Depending on history table size this process can be slow. 
  
 === IBM DB2 connection encoding === === IBM DB2 connection encoding ===
Line 84: Line 102:
 When item property "Type of information"​ is changed, previous history and trend data will not be displayed in graphs. When item property "Type of information"​ is changed, previous history and trend data will not be displayed in graphs.
  
---------------------------------------------------+==== See also ==== 
 + 
 +  * [[:​manual/​installation/​template_changes|Template changes]]