Zabbix 6.0.0 is not released yet.
The new version comes with a native high availability solution for Zabbix server.
The solution consists of multiple zabbix_server instances or nodes, where only one node can be active (working) at a time, while other nodes are on standby, ready to take over in case the current node is stopped or fails.
See also: High availability cluster.
Several updates have been made in the new version to the high-level overview of the monitored infrastructure offered by the services functionality.
The availability of services in previous Zabbix versions depended on triggers and their states. In the new version that is replaced by a tag-based mapping to problems for the respective service.
The configuring and viewing of services is now merged in Monitoring → Services, and a separate section for service configuration no longer exists in Configuration → Services.
In service configuration, hard and soft dependencies no longer exist. Instead, a service can have multiple parent services.
There are new status calculation rules and flexible additional rules for calculating the status of a parent service based on the statuses and weight of direct children. It is now also possible to set flexible rules for propagating a service status to parent services.
Flexible permissions to services have been implemented on user role level. Read-write or read-only access can be granted to all, none or selected services (based on name or tags).
A new Root cause column lists the underlying problems that directly or indirectly affect the service status.
If you click on the problem name you can see more details about it in Monitoring → Problems.
It is now possible to receive automated alerts about service status changes, similar to the alerts about trigger status changes.
A new service action type has been added to the Actions menu. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem escalation scenarios.
New message templates Service, Service recovery, and Service update have been added to media types and should be defined to enable correct sending of notifications for service actions.
Services now can be cloned. The Clone button has been added to the configuration form of a service. When a service is cloned, its parent links are preserved, while the child links are not.
Primary keys are now used for all tables, including history tables, in new installations.
There is no automatic upgrade to primary keys for existing installations. Instructions for a manual upgrade of history tables to primary keys in pre-existing installations are available for MySQL/MariaDB, PostgreSQL, TimescaleDB v1 and v2, and Oracle.
An Item value widget has been added to dashboard widgets.
This type of widget is useful for displaying values of single items prominently. Different visual styles of display are possible:
For more information, see Item value widget.
New macros are now supported for trigger expression debugging and internal actions.
Expression debugging macros simplify the process of debugging trigger expressions:
Macros for internal actions contain the reason why an item, an LLD-rule, or a trigger became unsupported:
For more details, see Supported macros.
A new expression syntax for triggers and calculated items was introduced in Zabbix 5.4. However, the old syntax still remained in use in simple macros. In the new version, the functionality of simple macros has been transferred to expression macros and the new expression syntax is used. See the comparison below for details of the change:
|In Zabbix 6.0||Before Zabbix 6.0|
Example of an expression macro in the new version.
Example of a simple macro in previous versions.
The existing simple macros will be converted to expression macros during the upgrade. The scope of expression macros covers the same that was offered by simple macros. Thus, expression macros can be used in:
The support for positional macros in item name ($1, $2...$9), deprecated since Zabbix 4.0, has been fully removed.
The support for user macros in item names (including discovery rule names), deprecated since Zabbix 4.0, has been fully removed.
Bulk processing of dependent items has been introduced in the preprocessing queue to improve the performance of retrieving Prometheus metrics.
See Prometheus checks for more details.
A Prometheus pattern step in the preprocessing can produce a result where multiple lines are matched. To handle this situation, a new result processing parameter has been added to the Prometheus pattern preprocessing step that allows to aggregate the data of potentially multiple matching lines by introducing functions such as sum, min, max, avg, and count.
It has been possible to collect Prometheus metrics in Zabbix for a while now, but some of the metrics are difficult to work with. Specifically, the metrics of histogram type can be presented in Zabbix as multiple items with the same key names, but different parameters. However, even though such items are logically related and represent the same data, it has been difficult to analyze the collected data without specialized functions. To cover this functionality gap in the new version, rate() and histogram_quantile() functions, producing the same result as their PromQL counterparts, have been added.
Other new additions to complement this functionality are the bucket_rate_foreach() and the bucket_percentile() functions. For more information see:
It is now possible to check for monotonic increase or decrease in item values using the new monoinc() or monodec() history functions.
A new history function changecount() has been added allowing to count the number of changes between adjacent values. The function supports three different modes for counting all changes, only decreases, or only increases. As an example, it can be used to track changes in the number of users or the number of system uptime decreases.
Zabbix 5.2 introduced new trend functions useful for baseline monitoring. However, they still require defining relative thresholds (e.g. check that web traffic in September, 2021 is less than 2x higher compared to September, 2020). There are use cases when such thresholds are hard to define. For instance, the web traffic of a new but highly popular web site can organically grow many times over a year but the growth rate is unknown. Yet, a sudden traffic spike due to DDOS attack must generate an alert regardless of organic traffic growth.
Anomaly detection algorithms do exactly this - find data that don't look normal (outliers) in a context of other values.
New history function trendstl() has been added which uses 'decomposition' method to calculate the anomaly rate. It splits a single time series sequence into three other sequences:
Anomaly detection works with remainder sequence and checks if there are values that are too far from the majority of remainder values. "Far" means that the absolute value from the remainder sequence is N times greater than the standard or mean deviation.
Item configuration form now automatically suggests the matching type of information, if selected item key returns data only of the specific type (for example, log item requires Type of information: Log). Type of information parameter is now located under the Key parameter on the primary Item tab and is duplicated on the Preprocessing tab if at least one preprocessing step is specified. If Zabbix detects a possible mismatch of the selected type of information and key, a warning icon will be displayed next to the Type of information field.
Several new items have been added to Zabbix agent/agent 2:
modeparameter (crc32, md5, sha256)
modeparameter (bytes or lines)
For more details see agent items.
User parameters now can be reloaded from the configuration file without restarting the agent. To do so, run the new
userparameter_reload runtime control option, e. g.:
UserParameter is the only agent configuration option that will be reloaded with this command.
Each Zabbix agent 2 plugin now has a separate configuration file. By default, these files are located in the
./zabbix_agent2.d/plugins.d/ directory. The path is specified in the
Include parameter of the agent 2 configuration file and can be relative to the zabbix_agent2.conf or zabbix_agent2.win.conf file location.
Custom password complexity requirements can now be provided for Zabbix internal authentication method. To prevent Zabbix users from setting weak passwords, it is possible to enforce the following restrictions:
To create the optimal user experience and ensure the best Zabbix performance in various production environments, the support of some older database releases has been dropped. This primarily applies to the database versions that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance.
Starting from Zabbix 6.0, the following database versions are officially supported:
By default, Zabbix server and proxy will not start if an unsupported database version is detected. It is now possible, though not recommended, to turn off DB version check by modifying AllowUnsupportedDBVersions configuration parameter for the server or proxy.
utf8mb4 encoding with utf8mb4_bin collation is now supported for Zabbix installations with the MySQL/MariaDB database.
Previously only utf8 encoding was supported, which with MySQL stands for utf8mb3 encoding and thus supports only a subset of proper UTF-8 characters. In the new version utf8mb4 support has been added with support for the full UTF-8 character set. Old installations using utf8mb3 are kept intact and may continue using that encoding.
Zabbix get and Zabbix sender utilities now support a
-t <seconds> or
--timeout <seconds> timeout parameter. The valid range is:
The ability to handle compressed content has been added to Zabbix web monitoring. All encoding formats supported by libcurl are supported.
Zabbix Prometheus preprocessing query language now supports two additional label matching operators:
The audit log now contains records about all configuration changes for all Zabbix objects, including changes that occurred as a result of executing an LLD rule, a network discovery action, an autoregistration action, or a script execution. Previously, configuration changes initiated from Zabbix server, for example, as a result of executing a discovery rule, were not recorded. Now such object modifications will be stored as audit records attributed to the user System.
A functionality for filtering records by the frontend operation that caused these entries has been added. If several log records have been created as a result of a single operation, for example, linking/unlinking a template, such records will have the same Recordset ID.
New section Audit log has been added to the Administration→General menu allowing to enable or disable audit logging. Housekeeping settings for audit, previously located under the Housekeeper section, have also been moved to the new Audit log section.
Support for PCRE2 has been added and Zabbix installation packages for RHEL/CentOS 7 and newer, SLES (all versions), Debian 9 and newer, Ubuntu 16.04 and newer have been updated to use PCRE2. PCRE is still supported, but Zabbix can only be compiled with one of the libraries PCRE or PCRE2, both cannot be used at the same time.
Processing ODBC checks has been moved from regular poller processes to separate server/proxy processes ODBC pollers. This change allows limiting the number of connections to the database created by poller processes. Previously, ODBC checks were performed by regular pollers, which also work with Zabbix agent items, SSH checks, etc.
You can use internal item zabbix[process,<type>] to monitor ODBC pollers load.
New official templates are available for monitoring:
You can get these templates:
To make template linking more visible, it is now placed in the first tab of the host, host prototype and template configuration forms and host/template mass update forms.
Consequently, a separate tab for template linking has been removed from all the respective forms.
In a related development, in host prototype configuration the fields for host group/host group prototype selection have also been moved from a separate tab to the first tab.
It is now also possible to create new hosts from Monitoring → Hosts.
The Create host button is available for Admin and Super Admin users.
The form for host creation and editing is now opened in a modal (popup) window, in Configuration → Hosts, Monitoring → Hosts and in any page, where there is a host menu or other direct link to the host configuration.
Direct links to the host edit page still work and are opening the host edit page in full page.
When configuring action operations, it is now possible to cancel notifications about canceled escalations by unmarking the checkbox of the corresponding option.
The Overview section in the Monitoring menu has been removed completely. The same functionality can be still accessed by using the Data overview and Trigger overview dashboard widgets.
The Latest data section now shows the time since last check (for example, 1m 20s) instead of the last item execution time. Additionally, it is now possible to view a raw value of an item without units or value mapping applied by hovering over the last value.
Audit log functionality has been reworked significantly. The updated Audit log contains records of all configuration changes of Zabbix objects and has an improved filter, which allows to view records grouped by frontend operation. Logging can be switched on or off in the Administration→General menu section. In order to implement these changes, the previously existing database structure had to be reworked. During an upgrade DB tables
auditlog_details will be replaced by the new table
auditlog with a different format. Existing audit log records will be deleted.
Zabbix server and proxy will now check the database version before launch and will not start if the version is out of the supported range. It is possible to turn off this check by modifying AllowUnsupportedDBVersions configuration parameter, but this approach is not recommended. The list of officially supported database versions has been updated to exclude databases that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance.
Zabix now supports both PCRE and PCRE2. Zabbix packages for RHEL/CentOS 7 and newer, SLES (all versions), Debian 9 and newer, Ubuntu 16.04 and newer have been updated to compile with PCRE2 instead of PCRE. When compiling from sources, users can choose to specify ''--with-libpcre'' or ''--with-libpcre2'' flag. If you are upgrading an existing installation, changing PCRE to PCRE2 may lead to some regular expressions behaving differently - see Known issues for details.