Zabbix Documentation 2.2

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:installation:upgrade_notes_220

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_220 [2014/09/25 15:11]
sasha Links adapted because of a move operation
manual:installation:upgrade_notes_220 [2017/02/16 10:09] (current)
martins-v note about case-sensitive MySQL database
Line 7: Line 7:
   * The "​mysqli"​ PHP extension is required instead of "​mysql"​   * The "​mysqli"​ PHP extension is required instead of "​mysql"​
   * Accepted data limit when using Zabbix protocol was changed from 128MB to 64MB.   * Accepted data limit when using Zabbix protocol was changed from 128MB to 64MB.
 +
 +=== 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.
  
 === New upgrade procedure === === New upgrade procedure ===
Line 19: Line 23:
  
 Since Zabbix 2.2 "​Read-write"​ permissions have precedence over "​Read"​ permissions. Previously, if a user (through two different user groups) had both "​Read"​ and "​Read-write"​ permissions to a specific host, the host was only "​Read"​ to them. Now it will be "​Read-write"​. Since Zabbix 2.2 "​Read-write"​ permissions have precedence over "​Read"​ permissions. Previously, if a user (through two different user groups) had both "​Read"​ and "​Read-write"​ permissions to a specific host, the host was only "​Read"​ to them. Now it will be "​Read-write"​.
 +
 +=== Trigger calculation changes with item history=0 ===
 +
 +Previously you could set the //Keep history// option in item configuration to 0 and still have those triggers working that used only the last value in calculation. Starting with the introduction of [[:​manual/​introduction/​whatsnew220#​value_cache_for_faster_access_to_history_data|value cache]] in Zabbix 2.2, no trigger functions will be calculated if item history is set to 0.
  
 === Changed maintenance period logic === === Changed maintenance period logic ===
Line 121: Line 129:
 The **DisableHousekeeping** server configuration option is supported no more. Instead, finer controls are located in the frontend, in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general|Housekeeper]]//,​ allowing to selectively enable/​disable housekeeping processes for specific tables. The **DisableHousekeeping** server configuration option is supported no more. Instead, finer controls are located in the frontend, in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general|Housekeeper]]//,​ allowing to selectively enable/​disable housekeeping processes for specific tables.
  
-<note warning>​Housekeeper is disabled by default after upgrading ​to 2.2. The desired housekeeper ​functionality ​should ​be enabled manually.</​note>​+Due to the changes in how latest item values are stored, values of items with history storage period set to "​0"​ will not be displayed in the //​Monitoring -> Latest data// and //​Monitoring -> Overview// pages. The //​{ITEM.LASTVALUE}//​ macro in the frontend will also not work for such items. To avoid breaking this functionality ​the history storage period will be automatically changed from "​0"​ to "​1"​ for all existing items.
  
 +<note warning>​Housekeeper is disabled by default after upgrading to 2.2. The desired housekeeper functionality should be enabled manually.</​note>​
 === JSON validation in server === === JSON validation in server ===
  
Line 171: Line 180:
  
 Zabbix server now correctly enables SSL host verification when using Ez Texting service to send alerts. Zabbix server now correctly enables SSL host verification when using Ez Texting service to send alerts.
 +
 +=== Queue changes ===
 +As the queue (Administration → Queue) is now retrieved directly from the server it is available only when Zabbix server is running and if the frontend has direct access to Zabbix server.
 +
 +=== Logging changes ===
 +
 +Before Zabbix 2.2.0, server and proxy would log messages about the availability of a particular type of checks on a host in the following format:
 +  SNMP item [ifInOctets.3] on host [gateway] failed: first network error, wait for 15 seconds
 +Starting with Zabbix 2.2.0, the type specification for SNMP, IPMI and JMX checks now includes the additional word "​agent":​
 +  SNMP agent item [ifInOctets.3] on host [gateway] failed: first network error, wait for 15 seconds