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/08/31 14:44]
andris [10 Changes in evaluation of trigger and calculated item expressions] section added
manual:installation:upgrade_notes_320 [2019/02/12 06:39] (current)
martins-v formatting change
Line 1: Line 1:
-==== Upgrade notes for 3.2.0 ====+==== 10 Upgrade notes for 3.2.0 ====
  
-<note warning>​​Zabbix 3.2.0 is not released yet.</​note>​+These notes are for upgrading from Zabbix 3.0.x to Zabbix 3.2.0. ​All notes are grouped into:
  
-<note important>​If upgrading from Zabbix 2.4, make sure to read the upgrade ​notes for [[https://​www.zabbix.com/​documentation/​3.0/​manual/​installation/​upgrade_notes_300|Zabbix ​3.0]] as well.</​note>​+  * ''​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
  
-=== - Delaying escalations during maintenance ===+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.
  
-The logic of delaying problem notifications during host maintenance has been changed. ​+==== Critical ====
  
-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. +=== 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 [[:​manual/​introduction/​whatsnew320#​delaying_escalations_during_maintenance|has been changed]].  
 + 
 +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 16: Line 33:
   * 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
  
-=== Recovery operations ===+== 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 ===
  
 [[:​manual/​config/​notifications/​action/​recovery_operations|Recovery operations]] are a new unified way of executing scripts or getting notified on resolved problems. Before the only way to execute a script when problem triggers went OK was to configure an action to start an escalation on the '​Trigger value = OK' condition. This is not supported any more - an action with recovery operations must be used instead. [[:​manual/​config/​notifications/​action/​recovery_operations|Recovery operations]] are a new unified way of executing scripts or getting notified on resolved problems. Before the only way to execute a script when problem triggers went OK was to configure an action to start an escalation on the '​Trigger value = OK' condition. This is not supported any more - an action with recovery operations must be used instead.
Line 37: Line 59:
 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 === +=== IBM DB2 connection encoding ===
- +
-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 ===+
  
 When connecting to IBM DB2 database Zabbix server, proxy and frontend will now ensure that database server anticipates UTF-8 encoded text. Previously the way IBM DB2 server interpreted text information from Zabbix was fully determined by Zabbix server/​proxy or web server locale settings (LC_ALL, LANG, LC_CTYPE and other environment variables). If the latter were not configured properly text containing non-ASCII characters was saved in the database incorrectly. In such situations after upgrade non-ASCII characters will be displayed in Zabbix incorrectly. The problem could easily not manifest itself if locale was identically misconfigured for Zabbix server and for web server running Zabbix frontend and the number of non-ASCII characters was too low to cause "Value too long..."​ errors. Please check the database contents before upgrading. When connecting to IBM DB2 database Zabbix server, proxy and frontend will now ensure that database server anticipates UTF-8 encoded text. Previously the way IBM DB2 server interpreted text information from Zabbix was fully determined by Zabbix server/​proxy or web server locale settings (LC_ALL, LANG, LC_CTYPE and other environment variables). If the latter were not configured properly text containing non-ASCII characters was saved in the database incorrectly. In such situations after upgrade non-ASCII characters will be displayed in Zabbix incorrectly. The problem could easily not manifest itself if locale was identically misconfigured for Zabbix server and for web server running Zabbix frontend and the number of non-ASCII characters was too low to cause "Value too long..."​ errors. Please check the database contents before upgrading.
  
-=== Host availability,​ discovery, auto-registration and history data validation ===+=== Host availability,​ discovery, auto-registration and history data validation ===
  
 When Zabbix server had received invalid host availability,​ discovery or auto-registration data it used to write a warning to the log file for every invalid entry. Now in the case of invalid entries it will reject the whole data packet and log a single line like //proxy "<​proxy name>"​ at "<​proxy IP>"​ returned invalid host availability data[: <​detailed error message>​]//​ (for passive proxies) or //received invalid host availability data from proxy "<​proxy name>"​ at "<​proxy IP>":​ <​detailed error message>//​ (for active proxies). Also, if passive proxy for example returns invalid host availability data, server will skip polling discovery, history and auto-registration data from that proxy. Like before, Zabbix will try to process as much historical data from proxies and active agents as it can and will silently ignore invalid entries. If the whole packet is invalid a message containing name, IP address and error description will be logged. This will help tracking down misconfiguration issues when proxypoller connects server'​s trapper port or agent instead of proxy. When Zabbix server had received invalid host availability,​ discovery or auto-registration data it used to write a warning to the log file for every invalid entry. Now in the case of invalid entries it will reject the whole data packet and log a single line like //proxy "<​proxy name>"​ at "<​proxy IP>"​ returned invalid host availability data[: <​detailed error message>​]//​ (for passive proxies) or //received invalid host availability data from proxy "<​proxy name>"​ at "<​proxy IP>":​ <​detailed error message>//​ (for active proxies). Also, if passive proxy for example returns invalid host availability data, server will skip polling discovery, history and auto-registration data from that proxy. Like before, Zabbix will try to process as much historical data from proxies and active agents as it can and will silently ignore invalid entries. If the whole packet is invalid a message containing name, IP address and error description will be logged. This will help tracking down misconfiguration issues when proxypoller connects server'​s trapper port or agent instead of proxy.
  
-=== Miscellaneous ===+=== Miscellaneous ===
  
   * The customizable time period for displaying resolved problems/OK triggers and for blinking upon trigger status change has been limited to 86400 seconds (24 hours) in //​Administration//​ -> //General// -> //Trigger displaying options//.   * The customizable time period for displaying resolved problems/OK triggers and for blinking upon trigger status change has been limited to 86400 seconds (24 hours) in //​Administration//​ -> //General// -> //Trigger displaying options//.
  
-=== Logging changes ===+=== Logging changes ===
  
 The messages printed to the log files about completion of the trend data synchronization have been changed. The messages printed to the log files about completion of the trend data synchronization have been changed.
Line 62: Line 80:
   syncing trends data done -> syncing trend data done   syncing trends data done -> syncing trend data done
  
- +=== Item changes ===
-=== Item changes ===+
  
 **system.sw.os[name]** item might have different value on Linux systems. Now the PRETTY_NAME parameter from /​etc/​os-release file is used by default. Only if os-release is not supported by the system the /​etc/​issue.net file is used to obtain system name. **system.sw.os[name]** item might have different value on Linux systems. Now the PRETTY_NAME parameter from /​etc/​os-release file is used by default. Only if os-release is not supported by the system the /​etc/​issue.net file is used to obtain system name.
  
-=== - Template changes ​===+=== Changes in evaluating trigger and calculated item expressions ​===
  
-//Template OS Windows// has been extended with a ''​service.discovery''​ low-level discovery rule that contains a ''​service.info[{#​SERVICE.NAME},​state]''​ item prototype for service state monitoring.+Previously any unsupported item in trigger expression or error in function evaluation immediately rendered the whole expression value to //Unknown//.
  
-In order to extended it, import this template from https://​www.zabbix.org/​wiki/​Zabbix_Templates/​Official_Templates.+In the new version unsupported items and errors in function evaluation continue ​to take part in expression evaluation as unknown values.
  
-=== - Changes in evaluation of trigger and calculated item expressions === 
- 
-In earlier versions any unsupported item in expression or error in function evaluation immediately rendered the whole expression value to Unknown. 
- 
-In Zabbix 3.2 unsupported items and errors in function evaluation continue to take part in expression evaluation as unknown values. 
 These unknown values may turn into "​known"​ values in logical operations, e.g.: These unknown values may turn into "​known"​ values in logical operations, e.g.:
-  * '1 or Unsuported_item1.some_function()'​ is evaluated to 1 (True) +  * '1 or Unsuported_item1.some_function()'​ is now evaluated to '1' ​(True) 
-  * '0 and Unsuported_item1.some_function()'​ is evaluated to 0 (False) +  * '0 and Unsuported_item1.some_function()'​ is now evaluated to '0' ​(False) 
-   + 
-Functions ​**nodata()**,​ **date()**, **dayofmonth()**,​ **dayofweek()**,​ **now()** and **time()** are now calculated for unsupported items, too.+Additionally ​**nodata()**,​ **date()**, **dayofmonth()**,​ **dayofweek()**,​ **now()** and **time()** ​trigger functions ​are now calculated for unsupported items as well.
  
 See [[:​manual/​config/​triggers/​expression#​expressions_with_unsupported_items_and_unknown_values|Expressions with unsupported items and unknown values]]. See [[:​manual/​config/​triggers/​expression#​expressions_with_unsupported_items_and_unknown_values|Expressions with unsupported items and unknown values]].
---------------------------------------------------+ 
 +=== Changes in graphs after item data type is changed === 
 + 
 +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]]