Zabbix Documentation 3.2 (current)In development:4.2 (devel)Unsupported:

User Tools

Site Tools



7 What's new in Zabbix 3.2.2

7.1 Nested host group support

Nested representation of host groups was introduced in Zabbix 3.2.0. However, it was limited to assigning permissions to host groups and frontend filtering options.

Also, to select subgroups, a '/*' syntax had to be used after the parent group name. Now it is possible to select subgroups by simply:

  • entering the parent group name
  • entering the parent group name and selecting Include subgroups (in assigning user permissions to host groups)

More importantly, specifying a parent host group now implicitly selects all level-down host groups in several new locations:

  • aggregate checks - items of hosts from nested groups are included
  • action conditions - hosts from nested host groups are included
  • action operations - remote command is also executed on hosts from nested groups
  • correlation conditions - hosts from nested host groups are included
  • host maintenance - hosts from nested host groups are also included
  • global scripts - when checking if a script can be executed on a nested group, parent group is included

7.2 User macros in event tags

Options related to event tags (tag name, value and tag for matching) now may include user macros and user macro context. Low-level discovery macros can be used inside the user macro context.

Additionally, the limitation of using a '/' forward slash has been removed from event tag names.

7.3 Frontend improvements

7.3.1 Updated translations

  • English (United States)
  • Ukrainian

7.3.2 One-line display of problem and resolution

Having the problem event and its resolution event displayed in one line was introduced by the new MonitoringProblems section of Zabbix 3.2. Now this approach has been expanded to other related sections.

In MonitoringTriggers, when Show all events or Show unacknowledged events are selected in the filter, both problem time and recovery time (if any) are displayed in one line instead of simply showing the last change time.

Before Zabbix 3.2.2:

Note that the term “Resolved” is used when displaying resolved problem events instead of “OK”.

Event details accessed from MonitoringProblems now also display problems and their resolution in one line. More events in less space can be displayed as a result.

Before Zabbix 3.2.2:

Similarly, the history of events, available as a screen element, now displays problems and their resolution in one line.

Before Zabbix 3.2.2:

7.3.3 Miscellaneous

  • When exporting a template or a host with web scenarios, triggers and graphs based on the web scenario or step items are exported as well.
  • {HOST.*} macros used in web scenario configuration are now correctly resolved in several frontend locations, including MonitoringWeb, MonitoringLatest data, simple graphs, etc.
  • {HOST.*} macros in item key parameters are now also resolved for items without interfaces, resolving to either Zabbix agent, SNMP, JMX or IPMI interface of the host.
  • User macros are now resolved on allowed hosts even if the macros are defined on a template that the user does not have permissions to.

7.4 Daemon improvements

  • Active agent auto-registration events are not generated any more if there is no action for auto registration.
  • OpenSSL 1.1.0 support, it brings some new ciphersuites for PSK, enabling Perfect Forward Secrecy. See differences between OpenSSL 1.0.2c and 1.1.0 Ciphersuites
  • Item creation/update by low-level discovery now returns errors in case macro resolving cannot be fully accomplished (instead of making such items that will inevitably fail on later stages). A corresponding error message will be displayed in ConfigurationHostsDiscovery.

7.5 Item changes

7.5.1 VMware monitoring

A new key has been added to monitor VMware hypervisor health state rollup sensor. The vmware.hv.status key was reverted back to its original implementation and now uses the hypervisor overall status property.

A new vmware.hv.datastore.size key has been added to monitor VMware datastore capacity and free space.

7.5.2 Windows monitoring

A new vm.vmemory.size key has been added to monitor virtual memory statistics on Windows.

7.5.3 Chassis information

Changed system.hw.chassis key to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory.

7.6 Trigger functions

  • Support for suffixed values has been added to the threshold parameter of the timeleft() trigger function.
  • forecast() now supports negative values in the time parameter.