This is an old revision of the document!

5 What's new in Zabbix 5.4.0

Zabbix 5.4.0 is not released yet.

Naming in JavaScript objects

The 'CurlHttpRequest' object has been renamed to 'HttpRequest' for simplicity. The previous object naming is now deprecated and its support will be discontinued after Zabbix 6.0.

Methods also have been renamed for greater consistency with JavaScript:

New namingOld naming
log Log
addHeader AddHeader
clearHeader ClearHeader
getHeaders GetHeaders
get Get
put Put
post Post
delete Delete
setProxy SetProxy
getStatus Status

The previous method names are now deprecated and their support will be discontinued after Zabbix 6.0.

New, convenient aliases have been added for logging methods:

New aliasAlias to
console.log(object) Zabbix.log(4, JSON.stringify(object))
console.warn(object) Zabbix.log(3, JSON.stringify(object))
console.error(object) Zabbix.log(2, JSON.stringify(object))

See also: Additional JavaScript objects

Trend function cache

Previously, trend-based trigger functions (trendavg, trendcount, etc) would always use database queries to obtain the required data. In the new version, a trend function cache has been implemented allowing to cache the result of calculated trend functions. Zabbix server, when processing trend functions, will check the trend cache for the cached result. In case of failure the server will read data from database and cache the result.

The trend function cache may be help to decrease the database server load when triggers contain trend functions mixed with history or timer-based functions.

The trend function cache size may be adjusted using the new TrendFunctionCacheSize server parameter. A new zabbix[tcache,cache,<parameter>] internal item has been implemented to monitor the trend function cache effectiveness.

Direct connections to database removed from pollers

Direct connections to database have been removed from pollers, unreachable pollers and JMX pollers on Zabbix server/proxy.

Previously these connections were required for:

  • Calculated items, aggregate checks and several internal items
  • Host availability updates in case of Zabbix agent, SNMP, JMX items. Pollers, unreachable pollers, JMX pollers and the IPMI manager would update host availability directly in the database with a separate transaction for each host.
  • Additionally host availability would be updated by the proxy poller thread and trapper when receiving host availability from Zabbix proxy and the configuration syncer when resetting host availability (host status changed, host moved to a new proxy, Zabbix proxy not available for too long)

Now, to handle calculated, aggregate and internal checks a new poller type history poller has been introduced. A new StartHistoryPollers configuration parameter allows to customize the needed history poller instances. As each history poller requires a database connection, it is recommended to keep the number of instances as low as possible.

To deal with host availability updates, a new availability manager process has been introduced. All processes queue host availability updates to the availability manager and that queue is flushed by the availability manager to the database every 5 seconds.

You can monitor the new processes using the zabbix[process,<type>] internal item.


  • A new {ITEM.VALUETYPE} macro has been added returning the value type of the item. Possible values: 0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text.
  • Time period handling of the fmttime macro function has become more flexible.


Unified global event correlation form

The form for configuring global event correlation is now a single page where the fields from, previously, two tabs have been combined onto one page.


  • Mass update pages for hosts, templates, items, etc have been replaced by popup windows.
  • Import pages for importing templates, hosts, maps, etc have been replaced by import popup windows.
  • In global search results, all links are now visually separated under the Configuration and Monitoring headings.