8 What's new in Zabbix 5.0.3

VMware datacenter discovery

A new vmware.dc.discovery[url] item returns a JSON containing {#DATACENTER} and {#DATACENTERID} properties.

Host information in VMware event log

The information returned by the vmware.eventlog[<url>,<mode>] item now contains information about the source host, if such information is detected in the log.

Service checks on agent 2

Zabbix agent 2 items net.tcp.service[] and net.tcp.service.perf[] now support HTTPS and LDAP checks on Windows.

List of hosts linked to a template

Configuration → Templates section now displays number of linked hosts with a link to the host configuration section filtered by the template. Therefore it is possible to see all hosts connected to the template in a single-click.

New template

Template DB Oracle by ODBC is now available for out-of-the-box monitoring of the Oracle Database. To learn how to configure the template, please see setup instructions.

You can get this template:

  • In ConfigurationTemplates in new installations;
  • If you are upgrading from previous versions, you can download new templates from Zabbix Git repository or find them in the templates directory of the downloaded latest Zabbix version. Then, while in ConfigurationTemplates you can import them manually into Zabbix.

Latest data

  • Expanding/collapsing applications (absent in 5.0.2) has been re-implemented;
  • A 'Displaying N to N of N found' (e.g. Displaying 1 to 50 of 146 found) string has been added to the page allowing to estimate how many items of the total found are displayed and if items are displayed partially in the page.
  • For better page performance, the Show items without data filter option is now checked and disabled if no host is selected in the filter.

Monitoring of physical CPU utilization on IBM AIX

Zabbix agent for AIX has been enhanced with capability to monitor physical CPU utilization. A system.cpu.util[] item key now has an additional 4th parameter:

  • system.cpu.util[<cpu>,<type>,<mode>,<logical_or_physical>]

The <logical_or_physical> key parameter allows to specify whether an item should report logical or physical CPU utilization (supported values: logical, physical). See full item description.