Zabbix Documentation 3.4

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_340

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_340 [2018/02/16 11:19]
martins-v adding 'critical' and 'informational' headings to upgrade notes
manual:installation:upgrade_notes_340 [2019/02/12 06:39] (current)
martins-v formatting change
Line 3: Line 3:
 These notes are for upgrading from Zabbix 3.2.x to Zabbix 3.4.0. All notes are grouped into: These notes are for upgrading from Zabbix 3.2.x to Zabbix 3.4.0. All notes are grouped into:
  
-  * Critical - the most critical information related to the upgrade process and the changes in Zabbix functionality¬†+  * ''​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+  * ''​Informational'' ​- all remaining information describing the changes in Zabbix functionality
  
 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. 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.
Line 23: Line 23:
  
 ===  Additional dependencies === ===  Additional dependencies ===
-  * libpcre3 ​- the PCRE library is now mandatory when compiling Zabbix server. It is required for [[https://​en.wikipedia.org/​wiki/​Perl_Compatible_Regular_Expressions|Perl Compatible Regular Expression]] (PCRE) support. The naming may differ depending on the GNU/Linux distribution;​+  * libpcre ​- the PCRE library is now mandatory when compiling Zabbix server. It is required for [[https://​en.wikipedia.org/​wiki/​Perl_Compatible_Regular_Expressions|Perl Compatible Regular Expression]] (PCRE) support. The naming may differ depending on the GNU/Linux distribution, for example '​libpcre3'​ or '​libpcre1'​. Note that you need exactly PCRE (v8.x); PCRE2 (v10.x) library is not used;
   * libevent (version 1.4 or later) library is now mandatory: ​   * libevent (version 1.4 or later) library is now mandatory: ​
     * for Zabbix server always;     * for Zabbix server always;
Line 58: Line 58:
  
 If you have already manually URL-encoded values they will be left as is and will not be double URL-encoded. If you have already manually URL-encoded values they will be left as is and will not be double URL-encoded.
 +
 +=== Upgrading Java gateway ===
 +
 +Zabbix Java gateway has to be upgraded to support the new functionality of: 
 +
 +  * [[:​manual/​introduction/​whatsnew340#​configurable_jmx_endpoints|configurable JMX endpoints]];​
 +  * [[:​manual/​discovery/​low_level_discovery/​jmx|low-level discovery of JMX objects]].
 +
 +=== JMX item protocol changes ===
 +
 +An example of the new protocol:
 +
 +<​code>​
 +{"​request":"​java gateway jmx","​jmx_endpoint":"​service:​jmx:​rmi:///​jndi/​rmi://​127.0.0.1:​12345/​jmxrmi","​keys":​["​jmx[\"​java.lang:​type={#​FSNAME}\",​\"​HeapMemoryUsage.used\"​]"​]}
 +</​code>​
  
 ==== Informational ==== ==== Informational ====
Line 77: Line 92:
  
 See also: [[:​manual/​config/​visualisation/​maps/​map#​access_based_on_permissions|Network map configuration]] See also: [[:​manual/​config/​visualisation/​maps/​map#​access_based_on_permissions|Network map configuration]]
- 
-=== Upgrading Java gateway === 
- 
-Zabbix Java gateway has to be upgraded to support the new functionality of:  
- 
-  * [[:​manual/​introduction/​whatsnew340#​configurable_jmx_endpoints|configurable JMX endpoints]];​ 
-  * [[:​manual/​discovery/​low_level_discovery/​jmx|low-level discovery of JMX objects]]. 
- 
-=== JMX item protocol changes === 
- 
-An example of the new protocol: 
- 
-<​code>​ 
-{"​request":"​java gateway jmx","​jmx_endpoint":"​service:​jmx:​rmi:///​jndi/​rmi://​127.0.0.1:​12345/​jmxrmi","​keys":​["​jmx[\"​java.lang:​type={#​FSNAME}\",​\"​HeapMemoryUsage.used\"​]"​]} 
-</​code>​ 
  
 === Using templates for network devices === === Using templates for network devices ===
Line 173: Line 173:
 === API changes === === API changes ===
  
-Deprecated ''​isreadable()''​ and ''​iswritable()''​ methods as well as the ''​proxy.interfaces''​ parameter have been removed.+  * Deprecated ''​isreadable()''​ and ''​iswritable()''​ methods as well as the ''​proxy.interfaces''​ parameter have been removed.¬†
 +  * Validation of "​period"​ field has been added disallowing a trailing semicolon. All existing trailing semicolons will be removed by proxy/​server during upgrade.  ​
  
 === Changed housekeeper defaults === === Changed housekeeper defaults ===
Line 182: Line 183:
  
 Socket-based inter-process communication has been added in Zabbix 3.4. On systems where SELinux is enabled it may be required to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the ''​SocketDir''​ directory. Currently socket files are used by server (alerter, preprocessing,​ IPMI) and proxy (IPMI). Socket files are persistent, meaning are present while the process is running. Socket-based inter-process communication has been added in Zabbix 3.4. On systems where SELinux is enabled it may be required to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the ''​SocketDir''​ directory. Currently socket files are used by server (alerter, preprocessing,​ IPMI) and proxy (IPMI). Socket files are persistent, meaning are present while the process is running.
 +
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]