This is the documentation page for an unsupported version of Zabbix.
Is this not what you were looking for? Switch to the current version or choose one from the drop-down menu.

24 Upgrade notes for 3.0.14

Configurable URI validation

URI validation, introduced in Zabbix 3.0.11, now can be turned off/on in the new VALIDATE_URI_SCHEMES frontend constant.

Additionally:

  • Relative URLs are no longer validated against the URI scheme whitelist i.e. are always considered valid.
  • In URLs where macros are supported, delayed validation is used. If the URL after resolving the macros is not valid, then the link will not work.
  • URLs with invalid port numbers, like ftp://user@host:port are considered as invalid

Item changes

  • In system.cpu.util agent items user and nice time no longer include guest time and guest_nice time (on Linux kernels 2.6.24 and above)
  • vmware.eventlog items will now browse up to 1000 events (instead of 10) in search of events that have not yet been processed. Consequently, when catching up after some downtime Zabbix may cache up to 1000 events, which will increase the VMware cache usage right after startup. The new algorithm is also less tolerant to multiple vmware.eventlog items configured with the same VMware URL.
  • From now on, Zabbix internal item zabbix[java,,ping] will not become not supported if java gateway is misconfigured or java gateway is unreachable

If you have some actions configured for internal events to monitor zabbix[java,,ping], please change it to nodata trigger to continue monitoring the availability of java gateway.

Security improvements

  • From now on HttpOnly flag is set for all session cookies.