manual:installation:upgrade_notes_340

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_340 [2014/03/18 14:43]
manual:installation:upgrade_notes_340 [2017/05/03 05:32]
martins-v fixing typo
Line 1: Line 1:
 +==== 10 Upgrade notes for 3.4.0 ====
 +
 +<note warning>​Zabbix 3.4.0 is not released yet.</​note>​
 +
 +These notes are for upgrading from Zabbix 3.2.x to Zabbix 3.4.0.
 +
 +It is possible to upgrade to Zabbix 3.4.0 from versions before Zabbix 3.2.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions.
 +
 +=== Dropping SQLite support for server/​frontend ===
 +
 +SQLite is no longer supported as a backend database for Zabbix server and frontend. It is still supported for Zabbix proxy.
 +
 +===  Additional dependencies ===
 +IPMI monitoring now requires libevent (version 1.4 or later) library installed.
 +
 +=== 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.
 +
 +=== URL-encoding in web scenarios ===
 +
 +While [[:​manual/​introduction/​whatsnew340#​automatic_url-encoding|automatic URL-encoding]] is supported starting with Zabbix 3.4, values in existing scenarios will not be automatically converted to URL-encoding. If you want those values URL-encoded you have to edit the [[:​manual/​web_monitoring#​configuring_steps|scenarios]] manually using the new fields:
 +
 +  * move query variables from the URL into //Query fields//
 +  * move post variables from //Raw data// into //Form data//
 +
 +If you have already manually URL-encoded values they will be left as is and will not be double URL-encoded.
 +
 +=== Support of macros and time suffixes in time periods ===
 +
 +To allow for an extended macro and time suffix [[:​manual/​introduction/​whatsnew340#​support_of_macros_and_time_suffixes_in_time_periods|support]],​ several fields that previously stored their value in days have been converted to store the values **in seconds**, e.g.:
 +
 +  * History/​trend storage period in items and item prototypes
 +  * //Keep lost resources// setting in low-level discovery
 +  * Global housekeeping settings
 +
 +While the numeric values are adjusted automatically during an upgrade, it is a **different** case if the //Keep lost resources// setting contained a macro before the upgrade. Its value (in days) is no longer valid in this field and cannot be adjusted by simply appending '​d'​ to the macro, because that is not an allowed macro syntax. The macro value cannot be changed either, because the macro may be used in other places. Therefore in this case during an upgrade the //Keep lost resources// setting is automatically converted to the maximum value of 25 years. This is something to take care of manually after the upgrade.
 +
 +=== Parallel processing of alerts ===
 +
 +Previously all problem notifications were handled by one alerter process. In the new version, **parallel processing** of alerts is implemented. There is a new alert manager process that can distribute alerts to several "​worker"​ processes. The maximum number of concurrent sessions is configurable by the user.
 +
 +During an upgrade, the number of concurrent sessions is set as '​1'​ for all media types. For the e-mail media type, you may want to [[:​manual/​config/​notifications/​media/​email#​configuration|manually]] increase that or set to '​0'​ (unlimited) for faster processing of alerts.
 +
 +Additionally,​ the **SenderFrequency** parameter has been removed from server [[:​manual/​appendix/​config/​zabbix_server|configuration]]. The first alert is now sent much faster and, if any retries are needed, the frequency for resending is looked up in the [[:​manual/​config/​notifications/​media/​email#​configuration|media type]] configuration (//Attempt interval// parameter).
 +
 +=== IT services renamed to services ===
 +
 +Configuration and monitoring sections that previously were called "IT services"​ have been renamed to "​Services"​ to reflect the fact that a broader range of services can be measured, not only IT.
 +
 +===  Configuration parameters ===
 +
 +A new configuration parameter ''​SocketDir''​ has been added to Zabbix server and proxy configurations. This parameter points to the directory where internal Zabbix socket files are stored (/tmp by default). Server and proxy use different socket file names so it's safe to use the same ''​SocketDir''​ for server and proxy running on the same system. However, running multiple servers or proxies in the same system will require different ''​SocketDir''​ configurations.
 +=== Item value preprocessing options ===
 +
 +Item value preprocessing options have been [[:​manual/​introduction/​whatsnew340#​item_value_preprocessing|unified]] and expanded as a separate tab in item configuration. As a result, several of the previously separate preprocessing parameters in items/item prototypes have been dropped:
 +
 +  * //Data type//, //Use custom multiplier//​ and //Store value// fields
 +  * ''​data_type'',​ ''​multiplier''​ and ''​delta''​ fields in API
 +  * ''​data_type'',​ ''​multiplier''​ and ''​delta''​ tags in XML export
 +
 +During an upgrade, all of these properties in existing items/item prototypes are converted to the new preprocessing options automatically. Similarly, when importing XMLs from older versions, these options are converted to the new preprocessing options.
 +
 +Additionally,​ //Delta (simple change)// and //Delta (speed per second)// preprocessing options have been renamed to //Simple change// and //Change per second//.
 +
 +=== Syntax for selecting nested host groups ===
 +
 +If upgrading from Zabbix 3.2.0 and 3.2.1, note that the syntax for including nested subgroups has changed.
 +
 +In Zabbix 3.2.0 and 3.2.1 nested host groups are included with the parent host group, it the parent group is specified as ''​hostgroup/​*''​. Since [[https://​www.zabbix.com/​documentation/​3.2/​manual/​introduction/​whatsnew322|Zabbix 3.2.2]] and in Zabbix 3.4.0, the '/​*'​ syntax is dropped. Instead, nested host groups are included if simply the parent host group is specified as is. This means that a host group that is set, for example, in action conditions, now **silently** includes all its nested host groups.
 +
 +=== Protocol changes ===
 +
 +Communication protocol between the frontend side and server side has been changed. A new "​sid"​ parameter has been added to the request from frontend to server for script execution. This parameter takes the ID of session (authentication token) and it is used to check the user permissions to execute scripts. Also, an additional check for host permissions (READ/​WRITE,​ READ and DENY) in the script has been added to this request. If the necessary access rights to the host are missing, the server will return a response that access to execute the script is denied.
 +
 +=== API changes ===
 +
 +Deprecated ''​isreadable()''​ and ''​iswritable()''​ methods as well as the ''​proxy.interfaces''​ parameter have been removed.
 +
 +=== Command/​script execution changes ===
 +
 +Due to command/​script exit code check [[manual/​introduction/​whatsnew340#​return_code_check_for_scripts_and_commands|introduction]] in Zabbix 3.4, [[manual/​config/​notifications/​media/​script|alertscripts]] can be executed multiple times if their exit code is different from 0. Previously configured items with user parameters executed by Zabbix server, external check items, and **system.run** items which exit code is not 0 may become “Not supported” due to additional checks for exit code, behavior of the items with "​nowait"​ flag is not changed though.
 +
 +=== Changed housekeeper defaults ===
 +
 +The default data storage period for internal, discovery and agent auto-registration events has been decreased from 365 days to 1 day. When upgrading from previous versions, it is recommended to decrease these values to 1 day manually as it can improve Zabbix server performance.
 +