A modern vertical menu in a sidebar replaces the horizontal menu in the new version.
The menu can be collapsed or hidden completely:
When the menu is collapsed, a full menu reappears as soon as the mouse cursor is placed upon it. Even when the menu is hidden completely, a full menu is just one mouse click away.
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 (template item, item prototype, low-level discovery rule) from the user interface even before saving and, if configured correctly, get a real value in return.
Item testing is not supported for active items and some simple checks (
To test the item, click on the Test button at the bottom of the item configuration form.
The item testing form has fields for the required host parameters (host address, port, proxy name/no proxy). These fields are context aware:
To test the item, click on Get value. If the value is retrieved successfully, it will fill the Value field.
A successfully retrieved value from host can also be used to test the preprocessing steps.
In fact, the item testing form is an extension of the preprocessing testing form already known in recent Zabbix versions. So if previously you could test preprocessing steps only against a hypothetical input value, now it is also possible to test preprocessing against a real test value just received.
To test the preprocessing steps against the real value, click on Get value and test.
In a related development the Check now option has been renamed to Execute now.
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.
Binary64 floating point numbers are now supported in new installations. For upgraded installations, a manual patch must be applied for binary64 floating point number support.
connection string parameter has been added to
db.odbc.* items. Now Database monitor items can be configured in two ways:
A new item value preprocessing option has been added allowing to find and replace a specified string with another:
This step has two parameters:
A new Zabbix sender option
allows to support nanoseconds in a Zabbix sender input file. This option can be only used together with the
--with-timestamps option, e.g.:
zabbix_sender -z 127.0.0.1 --with-timestamps --with-ns -i values.txt
This option specifies that each line of the input file contains the following, whitespace-delimited:
<host> <key> <timestamp> <ns> <value>, e.g.:
Zabbix server" trap001 1429533600 748744024 43 Zabbix server" trap001 1429533600 748791234 44
It is now possible to configure secure TLS connections to MySQL and PostgreSQL databases from:
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:
It is now possible to specify default message templates for each event type when defining Media types
SNMP version and credentials in previous versions were set at an item level. In the new version, all of these can be set at a host interface level:
See also: Configuring SNMP monitoring
When creating an item, the item type dropdown no longer has three entries for SNMP v1, v2 and v3 agent. Instead there is just an SNMP agent type and the ability to select the SNMP interface as required.
Zabbix server and Zabbix proxy now support an
-R snmp_cache_reload runtime control option, which reloads the SNMP cache and clears the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts. Net-SNMP version 5.3.0 or higher is required.
Macro value field now has Secret text mode. If enabled, it masks the content of a macro with asterisks to protect sensitive information, such as passwords or shared keys.
The following macros are now supported:
For more details, see Macros supported by location.
The IBM DB2 database is no longer supported by Zabbix.
The minimum required versions for supported databases now are:
TimescaleDB native compression is now supported in Zabbix server installations with PostgreSQL version 10.2 or higher and TimescaleDB version 1.5 or higher.
New official templates are available for monitoring:
You can get these templates:
The minimum required PHP version has been upped from 5.4.0 to 7.2.0.
Microsoft Internet Explorer 11 is no longer supported by Zabbix.
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:
The new frontend section Monitoring → Hosts provides detailed view of all monitored devices in a single location. To simplify the navigation Web and Graphs sections have been removed from the top menu in Monitoring. Both sections can now be accessed by clicking on respected links in Monitoring → Hosts section.
The following information is available from Monitoring → Hosts:
Links in the list above provide a convenient way to view corresponding page with more details about the given host. Users with admin and superadmin rights can also quickly navigate to the host's configuration page from the section. See this page for more details.
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.
Problems displayed in the Monitoring→ Problems section can now be filtered by one or several individually selected severities. Previously, there was only filtering by minimum severity level available.
Remote command logging, if enabled on Zabbix agent/agent2 (LogRemoteCommands=1) will no longer create log entries for system.run if it is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem parameters. system.run commands will be logged only if executed remotely.
Support of the mbedTLS (PolarSSL) crypto library has been discontinued.
Support of tabular data objects in JMX Mbean attributes has been added. It is supported for the JMX agent data collection and low-level discovery.