Global scripts now support custom logic written in JavaScript with the ability to call external HTTP services.
To configure JavaScript code as global script, select the new Webhook script type:
The Webhook script type offers three fields for adding the parameters, the JavaScript code and timeout.
Additionally, all defined global scripts now can be executed from the event menu.
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
Support of API authorization tokens has been added. Now it is possible to access Zabbix API using either a token or a Zabbix username and password for authorization. An opportunity to allow/deny management of API tokens has been added to user role permissions. Super admins with sufficient permissions can create and manage API tokens in the Administration→General frontend section or via the new token.*
API methods. Other users with permission to manage API tokens can view tokens assigned to them in user settings or via API.
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 naming | Old naming |
---|---|
log | Log |
addHeader | AddHeader |
clearHeader | ClearHeader |
getHeaders | GetHeaders |
get | Get |
put | Put |
post | Post |
delete | Delete |
setHttpAuth | SetHttpAuth |
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 alias | Alias 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)) |
New JavaScript object XML has been added to provide an ability to extract data by XPath and convert XML to JavaScript object (JSON) and vice versa.
See also: Additional JavaScript objects.
New option XML to JSON has been added in item preprocessing and low-level discovery preprocessing.
Support of strong authentication and privacy protocols for SNMPv3 has been implemented.
For authentication:
For privacy:
Also, after the upgrade the existing SHA and AES protocols will be renamed to SHA1 and AES128 respectively.
See also: Configuring SNMP hosts
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”.
A new vmware.cl.perfcounter[<url>,<id>,<path>,<instance>]
item allows to retrieve VMware cluster performance counter metrics.
The following templates are now available for out-of-the-box monitoring:
You can get these templates:
templates
directory of the downloaded latest Zabbix version. Then, while in Configuration → Templates you can import them manually into Zabbix.Value mapping is now configured on template/host level, in the template and host configuration forms respectively. Global value mapping has been removed.
Additionally:
See also: Value mapping
In several frontend filters it is now possible to filter entities:
This is implemented by adding new operators “Exists”, “Does not exist”, “Does not equal” and “Does not contain” in the tag filter conditions.
These filtering changes are implemented in:
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.