This is an old revision of the document!
In previous Zabbix versions it was difficult to tell if a newly-configured item was configured correctly or not. For that you needed to wait until the item tried to gather some data.
In the new version it is possible to test the item from the user interface immediately and, if configured correctly, get a real value in return.
A successful test value can also be used to test preprocessing steps.
In fact, the item testing form is an extension of the preprocessing testing form from the previous version. If previously you could test preprocessing steps against a hypothetical input value, now it is also possible to test the steps against the real test value just received.
ipmi.get IPMI item has been added that returns a JSON with IPMI-sensor related information. This item can be used for the discovery of IPMI sensors.
The maximum allowed length of an item key has been raised from 256 to 2048 characters.
It is possible to restrict checks on the agent side by creating a whitelist or blacklist of allowed item keys.
Whitelist/blacklist is created using a combination of two new agent configuration parameters:
AllowKey=<pattern>- which checks are allowed; <pattern> is specified using a wildcard (*) expression
DenyKey=<pattern>- which checks are denied; <pattern> is specified using a wildcard (*) expression
See also: Restricting agent checks
A stronger bcrypt cryptography is now used for hashing user passwords instead of MD5. The change to the stronger cryptography after the upgrade is automatic, i.e. no effort on the user side is required. Note that passwords longer than 72 characters will be truncated.
It is now possible to specify an HTTP proxy when configuring a webhook. The new HTTPProxy parameter is listed in the webhook parameter list by default with an empty value.
When specifying the proxy value the same functionality as in the item configuration HTTP proxy field is supported.
It is now possible to mass unlink templates when using host or template mass update:
It is now possible to specify default message templates for each event type when defining Media types
The IBM DB2 database is no longer supported by Zabbix.
The minimum required versions for supported databases now are:
Some frontend sections in Zabbix may display a different page depending on user selection. For example, Administration → General may display twelve different pages.
Previously, the page selection was made in a rather small, easy-to-miss dropdown located in the top right corner of the page. Now that selection has been integrated into the headings on the left.
This change affects the following sections:
In several configuration sections of Zabbix frontend detail editing is now opened as a popup window. This is implemented for:
In many cases this change allows to de-clutter the interface of having to configure too many options in one screen. For example, details of an action operation are now opened in a separate popup window.