All data about host availability have been moved from the host level to the level of individual interfaces. If a host has several interfaces of the same type and one interface becomes unavailable, it does not affect the availability of any other interface of the same type.
The way that host availability is displayed has been changed:
zabbix[host,<type>,available]internal item now reports availability of the main interface of a particular type of checks
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 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.
In low-level discovery, it is now possible to set up filtering by the specified macro presence (or absence). Two new filter condition operators have been added: “exists” and “does not exist”.
When creating an Oracle database, it is no longer required to copy images to the Oracle host.
vmware.cl.perfcounter[<url>,<id>,<path>,<instance>] item allows to retrieve VMware cluster performance counter metrics.
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.
Items, triggers, graphs, low-level discovery rules, and web scenarios belonging to templates are now separated from the items, triggers, graphs, low-level discovery rules, and web scenarios belonging to hosts. Configuration section has been updated to reflect this change.
For template entities:
For host entities, some drop-down filter selectors have been replaced with buttons, not affecting the functionality; Host group selector now allows selecting only host groups that contain at least one host; Hosts selector now allows selecting hosts only.
Some sections of the main menu in Zabbix now have an additional menu level that appears upon a mouse-click. A small right arrow next to the section name indicates that this section has a third-level menu. This change affects only sections that contain multiple pages:
The third-level menu is introduced as a more visible alternative to the title dropdown on the top of a page. The title dropdown is also still available, therefore users can select any of the two options for navigating between pages.
PSK identity and PSK fields in host and proxy configuration are now write-only. Once saved, these values cannot be viewed again in the frontend or retrieved through API but can be replaced with new values. For hosts, PSK identity and PSK will no longer be exported.