To be compatible with Zabbix 6.4, Zabbix agent must not be older than version 1.4 and must not be newer than 6.4.
You may need to review the configuration of older agents as some parameters have changed, for example, parameters related to logging for versions before 3.0.
To take full advantage of the latest metrics, improved performance and reduced memory usage, use the latest supported agent.
Older Zabbix agents 2 from version 4.4 onwards are compatible with Zabbix 6.4; Zabbix agent 2 must not be newer than 6.4.
Note that when using Zabbix agent 2 versions 4.4 and 5.0, the default interval of 10 minutes is used for refreshing unsupported items.
To take full advantage of the latest metrics, improved performance and reduced memory usage, use the latest supported agent 2.
To be fully compatible with Zabbix 6.4, the proxies must be of the same major version; thus only Zabbix 6.4.x proxies are fully compatible with Zabbix 6.4.x server. However, outdated proxies are also supported, although only partially.
In relation to Zabbix server, proxies can be: - Current (proxy and server have the same major version); - Outdated (proxy version is older than server version, but is partially supported); - Unsupported (proxy version is older than server previous LTS release version or proxy version is newer than server major version).
Examples:
Server version | Current proxy version | Outdated proxy version | Unsupported proxy version |
---|---|---|---|
6.4 | 6.4 | 6.0, 6.2 | Older than 6.0; newer than 6.4 |
7.0 | 7.0 | 6.0, 6.2, 6.4 | Older than 6.0; newer than 7.0 |
7.2 | 7.2 | 7.0 | Older than 7.0; newer than 7.2 |
Functionality supported by proxies:
Proxy version | Data update | Configuration update | Tasks |
---|---|---|---|
Current | Yes | Yes | Yes |
Outdated | Yes | No | Remote commands (e.g., shell scripts); Immediate item value checks (i.e., Execute now); Note: Preprocessing tests with a real value are not supported. |
Unsupported | No | No | No |
Warnings about using incompatible Zabbix daemon versions are logged.
XML files not older than version 1.8 are supported for import in Zabbix 6.4.
In the 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.