Zabbix Documentation 2.2

3.04.04.24.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.4Guidelines

User Tools

Site Tools


Sidebar

manual:introduction:whatsnew2216

20 What's new in Zabbix 2.2.16

20.1 Frontend improvements

  • {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.

20.1.1 Updated translations

  • English (United States)
  • Spanish
  • Ukrainian
  • Vietnamese

20.2 Daemon improvements

  • Active agent auto-registration events are not generated any more if there is no action for auto registration.
  • Item creation/update by low-level discovery will now return 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.

20.3 Item changes

20.3.1 VMware monitoring

A new vmware.hv.sensor.health.state key has been added to monitor VMware hypervisor health state rollup sensor. The vmware.hv.status key, which was changed in Zabbix 2.2.10 to use health state rollup sensor, was reverted back to the pre-Zabbix 2.2.10 implementation and now uses the hypervisor overall status property.

20.3.2 Chassis information

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