Table of Contents
15 Upgrade notes for 7.0.4
Breaking changes
Changes in the resolution of certain built-in macros
The behavior of resolving the macros {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {EVENT.CAUSE.*}, {EVENT.TAGS.*}, and {EVENT.SYMPTOMS} has been corrected for consistency with other built-in macros. Now, they will resolve to *UNKNOWN* if an error occurs while evaluating their value.
As a result of this change, to ensure proper functionality, it is necessary to update the media types for the following integrations: iTop, Jira Service Desk, ManageEngine ServiceDesk, SolarWinds Service Desk.
This change may also affect any custom scripts or integrations using the abovementioned macros.
Database restore error with PostgreSQL/TimescaleDB after upgrade from 7.0.0-7.0.4
Using pg_restore to restore a PostgreSQL/TimescaleDB backup created in Zabbix 7.0.0-7.0.4 will result in a missing base36_decode function error, causing the restore to fail. This error occurs when restoring a backup created with pg_dump.
See known issues for details on fixing this issue manually before creating the backup.
If you have not upgraded to Zabbix 7.0.0 yet, note that there should be no such issues for upgrades from pre-7.0 Zabbix versions to 7.0.5. For upgrade instructions, see Upgrading TimescaleDB schema.
Requirements
libevent 2.0.10 required
The minimum required version of libevent has been raised to 2.0.10.
Databases
Database changes
A slow template cloning issue has been resolved by adding indexes for the uuid field. This change may cause long upgrade times on large datasets.
New index on auditlog table
A new index has been added to the auditlog table to improve database and frontend response times when filtering records by IP in the Audit log.
Note that users with large audit logs may experience extended upgrade times due to the database size.
Processes
Problems no longer cached without enabled services
The service manager no longer caches problems if there are no services enabled.
The service manager will check for enabled services in configuration cache during startup and cache problems only if there are enabled services; it will also detect when the first service is added/last service removed and will initialize/free the problem cache.