Zabbix Documentation 3.0

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:installation:upgrade_notes_300

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_300 [2017/03/16 06:01]
martins-v fixing typo
manual:installation:upgrade_notes_300 [2019/04/12 11:32] (current)
martins-v formatting change
Line 1: Line 1:
-==== Upgrade notes for 3.0.0 ====+==== 10 Upgrade notes for 3.0.0 ====
  
-These notes are for upgrading from Zabbix 2.4.x to Zabbix 3.0.0.+These notes are for upgrading from Zabbix 2.4.x to Zabbix 3.0.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.0.0 from versions before Zabbix 2.4.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.0.0 from versions before Zabbix 2.4.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions.
 +
 +==== Critical ====
 +
 +=== Minimum required PHP version ===
 +
 +The minimum required PHP version has been upped from 5.3.0 to 5.4.0.
 +
 +=== Support for IE8 dropped ===
 +
 +Support for Microsoft Internet Explorer 8 is not provided any more.
  
 === Case-sensitive MySQL database === === 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. 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.
 +
 +=== Configuration parameters related to logging ===
 +
 +As a new **LogType** configuration parameter has been [[:​manual/​introduction/​whatsnew300#​configuration_parameters|added]],​ it is  important to note that previously Zabbix would log to syslog/​eventlog by default if the LogFile parameter was empty. After the upgrade, Zabbix logs to file as default and the agent **will not** start if LogFile is not specified. To enable logging to syslog/​eventlog,​ LogType must be set to //system//.
 +
 +==== Informational ====
  
 === Item changes === === Item changes ===
Line 40: Line 59:
  
 Deprecated ''​exists()''​ and ''​getObjects()''​ methods as well as the selectHosts and expandData parameters of the several ''​get()''​ methods have been removed. See [[manual:​api:​changes_2.4_-_3.0|API changes from 2.4 to 3.0]] for details. Deprecated ''​exists()''​ and ''​getObjects()''​ methods as well as the selectHosts and expandData parameters of the several ''​get()''​ methods have been removed. See [[manual:​api:​changes_2.4_-_3.0|API changes from 2.4 to 3.0]] for details.
- 
-=== Changes in configuration parameters related to logging === 
-A new configuration parameter ''​LogType''​ has been added in Zabbix 3.0. This parameter accepts the following values: 
-  * ''​file''​ (default) - write log messages to file configured by ''​LogFile''​ parameter 
-  * ''​system''​ - write log messages to syslog (Unix-like systems) or eventlog (Windows) 
-  * ''​console''​ - write log messages to standard output (valid only when running in foreground mode) 
- 
-It is  important to note that previously Zabbix would log to syslog/​eventlog by default, if the LogFile parameter was empty. After an upgrade to 3.0, Zabbix logs to ''​file''​ as default and the agent **will not** start if LogFile is not specified, too. To enable logging to syslog/​eventlog,​ LogType must be set to ''​system''​. 
  
 === Daemon changes === === Daemon changes ===
Line 55: Line 66:
 == Default configuration file changes == == Default configuration file changes ==
  
-Default configuration files have been changed. Most changes do not affect existing installations,​ but a new installation or an automated process that uses those files might have to be adjusted. See [[manual/​introduction/​whatsnew300#​default_configuration_file_improvements|"What'​s ​New" page]] for a list of changed parameters.+Default configuration files have been changed. Most changes do not affect existing installations,​ but a new installation or an automated process that uses those files might have to be adjusted. See [[:manual/​introduction/​whatsnew300#​configuration_parameters|What'​s ​new]] in 3.0 for a list of changed parameters.
  
 //​MaxHousekeeperDelete//​ change will affect existing installations unless this parameter is specified in the configuration file. //​MaxHousekeeperDelete//​ change will affect existing installations unless this parameter is specified in the configuration file.
Line 67: Line 78:
 Log file rotation has been improved. This can result in a situation where the log file, after being rotated, is empty for some time. This could not happen before. Log file rotation has been improved. This can result in a situation where the log file, after being rotated, is empty for some time. This could not happen before.
  
 +== Database recovery message on DebugLevel=2 ==
 +
 +If database query fails the following message will be printed to log file: ''​database is down: reconnecting in 10 seconds''​. When database goes up ''​database connection re-established''​ will be printed. There were no such messages on //​DebugLevel//​=2 previously.
 +
 +== Time to delete lost low level discovery resources ==
 +
 +Server will now calculate the time when to delete lost low level discovery resources based on the time when it processes a discovery rule. Previously a discovery item time stamp was used for this purpose. The new logic is meant to save users from situations when the discovery item is sent via Zabbix sender with invalid time stamp. However, if the discovery item is checked via proxy and/or active agent and a delay occurs on its way to the server, this situation results in lost resources being deleted later compared to the old logic.
 +
 +== History cache changes ==
 +
 +History text cache and the related internal checks (''​zabbix[wcache,​text,<​mode>​]''​) were removed - the text data is now also stored in history cache. Depending on setup the ''​HistoryCacheSize''​ parameter in configuration file should be increased by the old ''​HistoryTextCacheSize''​ value.
 +
 +History index cache was added to index the data store in history cache. The index cache size is configured by ''​HistoryIndexCacheSize''​ configuration file parameter. The history index cache size determines the maximum number of items that can be stored in history cache while the history cache size determines the maximum number of item values that can be stored in history cache.
 +
 +When history index cache is full Zabbix exits with a corresponding error. In the worst case Zabbix must be able to store values from all items in history cache - so the index cache size must be large enough to index all items on system. The index cache size needs roughly 100 bytes to cache one item.
 +
 +The history index cache usage can be monitored with internal check ''​zabbix[wcache,​index,<​mode>​]''​. See [[manual:​config:​items:​itemtypes:​internal|Internal checks]] for details. ​
 +
 +== Action and action condition caching ==
 +Actions and action conditions are now stored in configuration cache. That means changing actions or their conditions does not affect action processing until configuration cache is synchronized.
  
 == Dropping Inetd Zabbix agent == == Dropping Inetd Zabbix agent ==
  
 The Inetd version of Zabbix agent (zabbix_agent) has been dropped as it did not seem to have any users. The Inetd version of Zabbix agent (zabbix_agent) has been dropped as it did not seem to have any users.
 +
 +== Running Windows agent in console mode ==
 +
 +Previously the Windows agent defaulted to running in console if no service management command line options were specified. Now to run Windows agent in console the ''​-f''​ command line option is required.
  
 == Changes in modules == == Changes in modules ==
Line 78: Line 113:
 == Numbered macro resolution == == Numbered macro resolution ==
  
-Server used to resolve {MACRO<​1-9>​} just like the ordinary {MACRO} in non-trigger-related locations. Now in such places only {MACRO} can be used, {MACRO<​1-9>​} won't be recognised. In trigger-related locations {MACRO<​1-9>​} can still be used to reference items and respective hosts in the order they appear in trigger expression. Resolution of {{HOST.HOST<​1-9>​}:​key.func()} in graph names was not affected.+Server used to resolve {MACRO<​1-9>​} just like the ordinary {MACRO} in non-trigger-related locations. Now in such places only {MACRO} can be used, {MACRO<​1-9>​} won't be recognised. In trigger-related locations {MACRO<​1-9>​} can still be used to reference items and respective hosts in the order they appear in trigger expression. Resolution of ''​%%{{HOST.HOST<​1-9>​}:​key.func()}%%'' ​in graph names was not affected.
 === Frontend changes === === Frontend changes ===
  
-The minimum required PHP version has been upped from 5.3.0 to 5.4.0. +  * //​Configuration//​ -> //Maps// | //Screens// | //Slide shows// is not available anymore. Instead, all configuration options for these entities have been moved to //​Monitoring//​ -> //Maps// and //​Monitoring//​ -> //Screens// (that includes both screens and slide shows) sections.
- +
-Support for Microsoft Internet Explorer 8 is not provided anymore. +
- +
-//​Configuration//​ -> //Maps// | //Screens// | //Slide shows// is not available anymore. Instead, all configuration options for these entities have been moved to //​Monitoring//​ -> //Maps// and //​Monitoring//​ -> //Screens// (that includes both screens and slide shows) sections.+
  
-Zeroes are not displayed any more in lists for entities with no items. Whereas previously a (0) would be displayed next to the entity in a table column, now nothing is displayed.+  * Zeroes are not displayed any more in lists for entities with no items. Whereas previously a (0) would be displayed next to the entity in a table column, now nothing is displayed.
  
 |Previous\\ version: ​ | {{:​manual:​introduction:​with_zeroes.png|}} | |Previous\\ version: ​ | {{:​manual:​introduction:​with_zeroes.png|}} |
 |Zabbix 3.0:  | {{:​manual:​introduction:​without_zeroes.png|}} | |Zabbix 3.0:  | {{:​manual:​introduction:​without_zeroes.png|}} |
  
-A hardcoded <​nowiki>​----</​nowiki>​[BULK ACKNOWLEDGE]<​nowiki>​----</​nowiki>​ string is no longer added to bulk acknowledgement messages by default.+  * A hardcoded <​nowiki>​----</​nowiki>​[BULK ACKNOWLEDGE]<​nowiki>​----</​nowiki>​ string is no longer added to bulk acknowledgement messages by default.
  
-In IT service configuration,​ when clicking on a service name to open a popup (displaying options for adding child, editing or deleting service), the service name is no longer displayed in the heading.+  * In IT service configuration,​ when clicking on a service name to open a popup (displaying options for adding child, editing or deleting service), the service name is no longer displayed in the heading.
  
-In the fullscreen view of //​Monitoring -> Triggers//, the //Triggers info// screen element is no longer displayed as the top line. Removing the extra element makes it consistent with other fullscreen views and improves performance of the page.+  * In the fullscreen view of //​Monitoring -> Triggers//, the //Triggers info// screen element is no longer displayed as the top line. Removing the extra element makes it consistent with other fullscreen views and improves performance of the page.
  
 |{{:​manual:​introduction:​triggers_full_screen.png|}} ​ | |{{:​manual:​introduction:​triggers_full_screen.png|}} ​ |
 |The //Triggers info// top line (above) is no longer displayed in full screen view in Zabbix 3.0  | |The //Triggers info// top line (above) is no longer displayed in full screen view in Zabbix 3.0  |
  
-Some field labels have been changed in screen [[:​manual/​config/​visualisation/​screens/​elements|element]] definition to be more intuitive and correct:+  * Some field labels have been changed in screen [[:​manual/​config/​visualisation/​screens/​elements|element]] definition to be more intuitive and correct:
  
 ^ Screen element ^ Field label change ^ ^ Screen element ^ Field label change ^
Line 113: Line 144:
 |Simple graph prototype ​ |Parameter -> Item prototype ​ | |Simple graph prototype ​ |Parameter -> Item prototype ​ |
  
-History screens displaying 11 seconds more data than the selected interval has now been fixed and history screens obey the interval strictly.+  * History screens displaying 11 seconds more data than the selected interval has now been fixed and history screens obey the interval strictly.
  
-Translation of the byte unit prefixes - K for kilobytes, M for megabytes, etc. - has been removed because the "​bytes"​ unit was not translated.+  * Translation of the byte unit prefixes - K for kilobytes, M for megabytes, etc. - has been removed because the "​bytes"​ unit was not translated.
  
-Frontend maintenance mode superglobal variable $_REQUEST['​warning_msg'​] has been replaced by $ZBX_GUI_ACCESS_MESSAGE. See [[manual:​web_interface:​maintenance_mode|maintenance mode page]] for details.+  * Frontend maintenance mode superglobal variable $_REQUEST['​warning_msg'​] has been replaced by $ZBX_GUI_ACCESS_MESSAGE. See [[manual:​web_interface:​maintenance_mode|maintenance mode page]] for details.
  
-Popup action menu is closed when user clicks outside of it.+  * Popup action menu is closed when user clicks outside of it.
  
-The global script result window is now displayed without a header (it used to display a //Result of "​script name"//​ string). The header is reinstated in version 3.0.3.+  * The global script result window is now displayed without a header (it used to display a //Result of "​script name"//​ string). The header is reinstated in version 3.0.3
 + 
 +  * [[manual/​introduction/​whatsnew300#​exporting_and_importing_value_maps|Changes in value mapping]] allow to preserve these settings for the imported/​exported hosts and templates. However, if you want to import host/​template with custom "Host status"​ value map created in previous Zabbix versions you should recreate this setting in //​Administration → General → Value mapping// before importing as this setting was [[manual/​introduction/​whatsnew300#​value_mapping_improvements|enhanced and renamed]] in Zabbix 3.0.    
 + 
 +  * User and user group permission form has been redesigned. Permissions are no longer displayed in colour-coded listboxes. 
 + 
 +  * When copying elements, the copy page (where you choose the copy target) is not showing the element count any more.
  
-[[manual/​introduction/​whatsnew300#​exporting_and_importing_value_maps|Changes in value mapping]] allow to preserve these settings for the imported/​exported hosts and templates. However, if you want to import host/​template with custom "Host status"​ value map created in previous Zabbix versions you should recreate this setting in //​Administration → General → Value mapping// before importing as this setting was [[manual/​introduction/​whatsnew300#​value_mapping_improvements|enhanced and renamed]] in Zabbix 3.0.    
 === Trigger function improvements === === Trigger function improvements ===
  
 A check for valid reference has been added for global regular expressions in **logeventid()**,​ **regexp()** and **iregexp()** trigger functions. If entered reference is not valid, due to misspelling or missing referenced global regular expression, the trigger will switch to unknown state and appropriate error message will be displayed. A check for valid reference has been added for global regular expressions in **logeventid()**,​ **regexp()** and **iregexp()** trigger functions. If entered reference is not valid, due to misspelling or missing referenced global regular expression, the trigger will switch to unknown state and appropriate error message will be displayed.
  
-=== Logging IP addresses of incoming/​outgoing ​connections between ​Zabbix ​server and Zabbix ​proxy ===+=== Logging IP addresses of connections between server and proxy ===
  
 The messages printed to the log files will now contain IP addresses of incoming/​outgoing connections between Zabbix server and Zabbix proxy. The messages printed to the log files will now contain IP addresses of incoming/​outgoing connections between Zabbix server and Zabbix proxy.
Line 192: Line 228:
   received configuration data from server at "<​IP>",​ datalen <​LENGTH>​   received configuration data from server at "<​IP>",​ datalen <​LENGTH>​
  
-=== Database recovery message on DebugLevel=2 === +==== See also ====
- +
-If database query fails the following message will be printed to log file: ''​database is down: reconnecting in 10 seconds''​. When database goes up ''​database connection re-established''​ will be printed. There were no such messages on //​DebugLevel//​=2 previously. +
- +
-=== Time to delete lost low level discovery resources === +
- +
-Server will now calculate the time when to delete lost low level discovery resources based on the time when it processes a discovery rule. Previously a discovery item time stamp was used for this purpose. The new logic is meant to save users from situations when the discovery item is sent via Zabbix sender with invalid time stamp. However, if the discovery item is checked via proxy and/or active agent and a delay occurs on its way to the server, this situation results in lost resources being deleted later compared to the old logic. +
- +
-=== History cache changes === +
- +
-History text cache and the related internal checks (''​zabbix[wcache,​text,<​mode>​]''​) were removed - the text data is now also stored in history cache. Depending on setup the ''​HistoryCacheSize''​ parameter in configuration file should be increased by the old ''​HistoryTextCacheSize''​ value. +
- +
-History index cache was added to index the data store in history cache. The index cache size is configured by ''​HistoryIndexCacheSize''​ configuration file parameter. The history index cache size determines the maximum number of items that can be stored in history cache while the history cache size determines the maximum number of item values that can be stored in history cache. +
- +
-When history index cache is full Zabbix exits with a corresponding error. In the worst case Zabbix must be able to store values from all items in history cache - so the index cache size must be large enough to index all items on system. The index cache size needs roughly 100 bytes to cache one item. +
- +
-The history index cache usage can be monitored with internal check ''​zabbix[wcache,​index,<​mode>​]''​. See [[manual:​config:​items:​itemtypes:​internal|Internal checks]] for details.  +
- +
-=== Action and action condition caching === +
-Actions and action conditions are now stored in configuration cache. That means changing actions or their conditions does not affect action processing until configuration cache is synchronized. +
- +
-==Running Windows agent in console mode === +
-Before 3.0 Windows agent defaulted to running in console if no service management command line options were specified. Now to run Windows agent in console the ''​-f''​ command line option is required.+
  
 +  * [[:​manual/​installation/​template_changes|Template changes]]