A modern vertical menu in a sidebar replaces the horizontal menu in the new version.
The menu can be collapsed or hidden completely:
|Collapsed menu with icons only.||Hidden menu.|
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. See additional details.
String comparison is now allowed in triggers, using the = (equal) and <> (not equal) operators.
So, for example, it is now possible to define triggers that create alarm if the strings returned by two items are different:
String comparison is also possible in calculated items.
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, to avoid confusing it with the item testing functionality.
No data triggers are now, by default, sensitive to proxy availability - the 'nodata' triggers will not fire immediately after a restored connection, but will skip the data for the delayed period.
Suppression is turned on:
You may also turn off sensitiveness to proxy availability, using the new second parameter, e.g.: nodata(5m,strict). In this case the function will work the same as before and fire as soon as the evaluation period (five minutes, in this case) without data is past.
It is also possible to monitor how long data are delayed on the proxy using the new
zabbix[proxy,<proxy name>,delay] internal item.
It is now possible to enhance Zabbix frontend functionality by adding 3rd party modules or by developing your own modules without the need to change the source code of Zabbix. See Modules for more information.
Dashboard widgets can be copied and pasted in the new version. They can be copy-pasted within the same dashboard, or between dashboards opened in different tabs.
A widget can be copied using the widget menu:
Then the copied widget can be used to create a new widget with the same properties. To paste a widget:
A copied widget can also be used to paste over an existing widget using the Paste option in the widget menu.
Several improvements have been made to make it easier to work with large numbers of hosts and other elements.
A consistent Zabbix feature in previous versions was the presence of many dropdowns for host and host group selection, and sometimes also for selecting other elements like graphs. Typical locations for these dropdowns included top of the page and popups. In the new version that has been changed in many locations (see the list of locations below):
|Top-of-the-page selection dropdowns before Zabbix 5.0.|
|Multi-select fields in the filter in the new version.|
Please see individual pages for details on changed host/host group/graph/etc selection:
It is now possible to filter out items, triggers, hosts and graphs or override their attributes during low-level discovery based on LLD object and prototype name.
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.
Numeric (float) data type now supports precision of approximately 15 digits and range from approximately -1.79E+308 to 1.79E+308 (with exception of PostgreSQL 11 and earlier versions). This is by default for new installations. For upgraded installations, a manual patch must be applied.
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.:
This option specifies that each line of the input file contains the following, whitespace-delimited:
<host> <key> <timestamp> <ns> <value>, e.g.:
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.
The list of low-level discovery rules previously was always linked to a single host, making it impossible to view all discovery rules in one place or filter the ones of a specific host group or those having errors.
In the new version, the list of low-level discovery rules contains a filter allowing to filter by host group, host, discovery item type, discovery rule state and other parameters. Additionally, the added first column in the list now always displays the host of the discovery rule.
It is now possible to:
It is now possible to specify default message templates for each event type when defining media types.
Thus default message editing no longer takes place when configuring action operations.
Several improvements have been made to the problem update screen used for problem acknowledgment and other problem update operations:
Problems may sometimes be acknowledged by mistake so to remedy this situation it is now also possible to unacknowledge problems. A problem may be unacknowledged in the problem update screen.
In the problem history list unacknowledgment gets a special icon:
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.
Email notifications related to the same event are now grouped into one thread.
Elasticsearch version 7.X is now supported. Support of older Elasticsearch versions has been dropped.
SAML 2.0 authentication is now supported for logging into Zabbix.
New integrations are available allowing to use the webhook media type for pushing Zabbix notifications to:
Zabbix agent 2, first introduced on an experimental basis in Zabbix 4.4, is now officially supported. The functionality of the agent 2 has been extended:
Agent 2 can now be compiled from sources on the Windows platform.
A Docker plugin for Zabbix agent 2 is now available as part of the out-of-the-box monitoring of Docker containers (see list of supported keys).
A Memcached plugin for Zabbix agent 2 is now available as part of the out-of-the-box monitoring of Memcached instances (see description).
A MySQL plugin for Zabbix agent 2 is now available as part of the out-of-the-box monitoring of MySQL instances (see description).
Passing a URI, username and password via plugin configuration parameters is now supported only for named sessions. As such, parameters in a format Plugins.<PluginName>.Uri, Plugins.<PluginName>.User, Plugins.<PluginName>.Password are no longer supported. Named session parameters in a format Plugins.<PluginName>.Sessions.<SessionName>.Uri, Plugins.<PluginName>.Sessions.<SessionName>.Password, Plugins.<PluginName>.Sessions.<SessionName>.User can be used.
Alternatively, a URI, username and password can be provided in the item key parameters directly.
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.
User macros can now be defined for host prototypes and LLD macros can be used in the macro value fields (the LLD macro will be resolved when a host is created from the prototype).
User macros are now supported in IPMI username and password fields in host configuration.
The following macros are now supported:
For more details, see Macros supported by location.
The IBM DB2 database can no longer be used as a back-end database for 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:
zabbix[stats,<ip>,<port>]internal item now also returns version of Zabbix server or Zabbix proxy
zabbix[version]internal item has been added returning the version of Zabbix server or Zabbix proxy
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.
In Zabbix 5.0:
Before Zabbix 5.0:
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 main 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 the minimum severity level available.
It is now possible to view log entries during a webhook media type test.
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.
Zabbix agent2 is now able to store collected data for active checks in a persistent buffer (disabled by default). The following configuration parameters have been added:
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.