Zabbix Documentation 5.0 (current)| In development:5.0 (devel)| Unsupported:

User Tools

Site Tools



This is an old revision of the document!

5 What's new in Zabbix 5.0.0

Zabbix 5.0.0 is not released yet.

Minimum required versions for databases updated

Minimum database versions required for Zabbix 5.0.0:

  • MySQL 5.5.62
  • MariaDB 10.0.37
  • PostgreSQL 9.2.24
  • Oracle 11.2

IPMI sensor discovery

A new 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.

Item key limit raised

The maximum allowed length of an item key has been raised from 256 to 2048 characters.

Restricting agent checks

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

Stronger cryptography for passwords

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.

Support of IBM DB2 dropped

The IBM DB2 database is no longer supported by Zabbix.

Using HTTP proxy in webhooks

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.

Mass unlinking of templates

It is now possible to mass unlink templates when using host or template mass update:

See also:

Default messages for each media type

It is now possible to specify default message templates for each event type when defining Media types


Page selection dropdown integrated into headings

Some frontend sections in Zabbix may display a different page depending on user selection. For example, AdministrationGeneral 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:

  • MonitoringOverview
  • MonitoringScreens
  • ConfigurationActions
  • AdministrationGeneral
  • AdministrationQueue

Detail editing as popup window

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.