This is an old revision of the document!
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.
|New naming||Old naming|
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 alias||Alias to|
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 have been removed from pollers, unreachable pollers and JMX pollers on Zabbix server/proxy.
Previously these connections were required for:
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.
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.