Zabbix Documentation 5.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:appendix:compatibility

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
manual:appendix:compatibility [2017/02/20 08:46]
manual:appendix:compatibility [2020/02/06 06:04] (current)
martins-v more precise wording
Line 1: Line 1:
 +==== 14 Version compatibility ====
  
 +=== Supported agents ===
 +
 +Zabbix agents starting with version 1.4 are compatible with Zabbix 5.0. However, you may need to review the configuration of older agents as some parameters have changed, for example, parameters related to [[https://​www.zabbix.com/​documentation/​3.0/​manual/​installation/​upgrade_notes_300#​changes_in_configuration_parameters_related_to_logging|logging]] for versions before 3.0.
 +
 +To take full advantage of new and improved items, improved performance and reduced memory usage, use the latest 5.0 agent.
 +
 +Note that Zabbix agent newer than 5.0 cannot be used with Zabbix server 5.0.
 +
 +=== Supported Zabbix proxies ===
 +
 +Zabbix 5.0.x server can only work with Zabbix 5.0.x proxies. Zabbix 5.0.x proxies can only work with Zabbix 5.0.x server.
 +
 +<note important>​It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies. For more information,​ see the [[:​manual/​installation/​upgrade|upgrade procedure]].</​note>​
 +
 +Warnings about using incompatible Zabbix daemon versions are logged.
 +
 +
 +=== Supported XML files ===
 +
 +XML files, exported with 1.8, 2.0, 2.2, 2.4, 3.0, 3.2, 3.4, 4.0, 4.2 and 4.4 are supported for import in Zabbix 5.0.
 +
 +<note important>​In Zabbix 1.8 XML export format, trigger dependencies are stored by name only. If there are several triggers with the same name (for example, having different severities and expressions) that have a dependency defined between them, it is not possible to import them. Such dependencies must be manually removed from the XML file and re-added after import.</​note>​