ZABBIX 3.2.0rc1





08 September 2016

Zabbix Team is pleased to announce the availability of Zabbix 3.2.0rc1, first release candidate of Zabbix 3.2.

Zabbix is an enterprise-class open source distributed monitoring solution. Zabbix is released under the GPL, thus it is free of charge for both commercial and non-commercial use. A complete text of the license is available at

This document contains the release notes for Zabbix 3.2.0rc1. Download it from

This release introduces major improvements and new functionality. A nice overview of the new functionality is at

This release is not for production. It is a Release Candidate!

Upgrade notes

Please read Zabbix 3.2.0 upgrade notes and upgrade procedure for migration details.

The following sections describe the release in details and provide late-breaking or other information that supplements its main documentation.

What's New in 3.2.0rc1
  • [ZBXNEXT-3206] added support of flexible item key parameters for aliases
  • [ZBXNEXT-3405] implemented timeline in Monitoring->Problems view
  • [ZBXNEXT-3353] implemented interface for history export through loadable modules and changed module loading to require only zbx_module_api_version() function
  • [ZBXNEXT-3423] removed ability to acknowledge OK events
  • [ZBXNEXT-3416] implemented event hidden tag display with hint box when there are more than 3 tags and better display of long tags and added event tag display in event details widget
  • [ZBXNEXT-3412] implemented mass update for trigger and trigger prototype tags and manual close
Fixes included into 3.2.0rc1
  • [ZBXNEXT-3101] fixed displaying fields of "Operations" tab in action edit form when adding new operation in IE
  • [ZBX-11171] updated database versioning for v3.2 release
  • [ZBXNEXT-3101] fixed sql errors while upgrade IBM DB2 database
  • [ZBX-11143] added missing space in CTrigger.php SQL query
  • [ZBX-6083] strings that are related to status of item, trigger and host prototypes was renamed "Enable" and "Status" => "Create enabled", "Disable" => "Create disabled", "Enabled" => "Yes", "Disabled" => "No"
  • [ZBXNEXT-3201] fixed displaying of "Actions" hintbox
  • [ZBXNEXT-3201] fixed "Actions" column in exported csv file from Monitoring->Problem page
  • [ZBX-11119] fixed use of uninitialized variable
  • [ZBX-11040] added "page navigation" context to translation strings "First" and "Last"; replicated translations for "First" and "Last" in "page navigation" context from 2.2 brancha
  • [ZBX-11035] fixed incorrect headers in screens "Status of Zabbix" => "System status", "Zabbix server info" => "Status of Zabbix"; renamed screen element select option "Server info" => "Status of Zabbix"
  • [ZBX-11070] disallowed zabbix admin accessing notifications of users that does not share any user group
  • [ZBX-11057] fixed drawing lines of items with scheduled interval when graph data is selected from trends
  • [ZBX-11050] changed translation strings "Enable event acknowledges" => "Enable event acknowledgement" and "Search/Filter elements limit" => "Limit for search and filter results"
  • [ZBX-11071] fixed closing success and error messages in IE
  • [ZBXNEXT-3101] fixed undefined index when adding a message to user in action operations
What's expected in 3.2.0

:: Event tags for greater flexibility

Custom tags for events are introduced in the new version. Custom event tags are implemented as a pair of the tag name and value. You can use only the name or pair it with a value. After the tags are defined on the trigger level, corresponding events get marked with tag data.

The tags can be use to implement service-centric approach to management of notifications and displaying of problems.

For more information see event tag section.

:: Global event correlation

New global event correlation module allows pre-processing of problems based on event tag information. As a result of pre-processing a new problem or older problems matching correlation rules can be closed automatically.

:: Event correlation on trigger level

Configuration of triggers was extended to support ability of closing problem only if OK and PROBLEM event tags match each other. That allows much more flexible matching of problems and recovery conditions for log monitoring and trap processing.

:: Ability to manually close problems

Some problems, if allowed on trigger level, can be closed manually from Zabbix UI. It greatly simplifies workflow for trap processing, also for processing of errors reported in log files.

:: Independent escalation for each problem event

Zabbix will process and escalate individually each problem generated by trigger having problem event generation mode set to 'multiple'.

:: Ability to customize macro values

Sometimes a macro may resolve to a value that is not necessarily easy to work with. It may be long or contain a specific substring of interest that you would like to extract. For these purposes, the new version comes with a new concept of macro functions.

For more information see macro functions section.

:: Coping with fast-growing log files

More advanced options are available for dealing with fast-growing log files.

An optional maxdelay parameter for log monitoring items, which can be used to set a time bracket that log records must be analyzed within - if it's impossible to analyze all records within the set time, older lines are skipped in favour of analyzing the more recent ones.

Also, two new agent items log.count and logrt.count that count the number of matched lines and return that number instead of the lines themselves.

:: Easier trigger hysteresis

A much easier way of defining trigger hysteresis is introduced by an optional second trigger expression called 'recovery expression' where you can separately define the conditions that have to be met for the trigger to return back to the OK state.

There is also more control over how OK events are generated. You can use the problem expression as basis (then it works the same way as before), the recovery expression as basis, or even select 'None' in which case the trigger will always remain in problem state if it goes into it.

Additionally, PROBLEM event generation mode for single/multiple problem events has been changed from a silent default/optional checkbox into an obvious two-way choice.

For more information see configuring a trigger and trigger hysteresis sections.

:: Delaying escalations during maintenance

The logic of delaying problem notifications during host maintenance has been changed. The old mechanism is dropped. Instead there is an new option in action configuration, which allows to pause notifications in the host maintenance phase if you wish so. If notifications are paused during maintenance, they get back on course after the maintenance, according to the escalation scenario.

For more information see maintenance and escalations section.

:: Viewable items, triggers, graphs created by LLD

Now entities created by low-level discovery are shown in a much more user-friendly way. It is possible to view the details of these items, triggers and graphs. Check-boxes are enabled to apply mass operations to them. Thus it is possible to enable/disable/delete them.

:: Web scenario export/import

When exporting hosts or templates into XML, web scenarios are now exported as well. When importing hosts/templates, there are options for creating new, updating existing and deleting missing web scenarios.

Now on you may easily share web scenarios on For example, export a template with the web scenarios into XML and upload to Then others can download the template and import the XML into Zabbix.

:: Front-end improvements

Several frontend sections have gained a filter allowing to search by name as well as status, type or mode. Host groups, templates and global scripts can now be searched by name.

Introduced new high-performance view of current, recently resolved problems and history of problems under Monitoring->Problems. Monitoring->Events no longer exists.

:: API improvements

New API method 'problem.get' is introduced to allow retrieval of problem related information.

:: Improvements for trigger functions

Added two new options "regexp" and "iregexp" to the third parameter <operator> of trigger function count().

:: More efficient table structure for history text and history log

Unused id field was removed to make history tables more efficient.

:: Enabled evaluation of function nodata() for not supported items

Function nodata() will be normally evaluated even if a corresponding item is unsupported for some reason.

:: Added evaluation of logical expressions with unsupported items in trigger expressions and calculated items

Zabbix will correctly evaluate trigger expressions if one of items is unsupported.

:: Added datacenter name for VMWare hypervisors and virtual machines

Introduced new items and Also added support of new discovery field {#DATACENTER.NAME} for hypervisor and virtual machine discovery.

:: Less verbose trap processing

Added one minute delay for repeated SNMP trap file error log entries.

:: Updated translations

Updated translations to many languages.

Installation and Upgrade Notes


See Zabbix Manual for full details.


Recompile Zabbix binaries and update front-end PHP files. Execute a database patch if migrating from Zabbix 1.8.x. See Zabbix Manual for a detailed upgrade procedure.

Commercial support

Zabbix Company provides a full range of professional services. We also provide trouble-free upgrade service for easy migration from earlier versions to Zabbix 2.2 LTS, Zabbix 3.0 LTS or Zabbix 3.2. Please contact Sales for pricing and more details.


Privacy Policy 商標ポリシー