Triggers and Monitoring → Events sections used for this purpose previously. 8 In a related development, Monitoring → Events has been removed from the frontend. To access event details, use the new section host group Note that nested host group functionality is extended in Zabbix 3.2.2. In a related development, the host group permission tab has been significantly reworked in user group and user configuration action property tab. Note that some action conditions have been dropped completely with this development: • ”Trigger value” conditions for trigger events • ”Event type” conditions for internal events

trigger prototypes has been optimized by reducing the number of SQL statements. As a result, the process of creating triggers takes only half of the time as before. 5.10 Multiple OID support in SNMP discovery Performance improvements The process of trigger expression evaluation has been improved dramatically by using a hashing mechanism. Also configuration cache locking during that process has been reduced multiple performance. 23 5.21 Item changes/improvements A new proc.cpu.util item has been added to monitor process CPU utilisation. This item is supported on Linux and Solaris platforms. net.udp.service and net

option has also been added to LDAP authentication details. See also: Authentication In a related development, an LDAP frontend access option has been added for user group configuration. More flexible active for Zabbix frontend: • High-contrast light • High-contrast dark |<| |<| |-| |<| Within this development, default colors for graphs in the dark themes have also been updated: • When creating a new graph collected only once for each datastore instead of one time per each hypervisor. 37 Within this development the following new items have been added: • vmware.datastore.discovery[] • vmware.datastore

the master item data. See also: Dependent items 5 Parallel processing of alerts A single alerter process was used in the previous versions to send problem notifications. Alerts were sent out one by one In the new version, parallel processing of alerts is implemented. There is a new alert manager process that can distribute alerts to several ”worker” processes, if needed. Media types are processed in Attempts and Retry interval: • Functionality of the database watchdog process has been merged into the alert manager and the watchdog process itself removed. 6 Improved notifications 6.1 Notification on problem

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . test. See also: • Testing an item • Testing preprocessing steps Execute now In a related development the Check now option has been renamed to Execute now, to avoid confusing it with the item testing central process of Zabbix software that performs monitoring, interacts with Zabbix proxies and agents, calculates triggers, sends notifications; a central repository of data. Zabbix proxy - a process that

to extract its value and set it as an error message for the item. 8 Throttling rules allow to process value only if it is changed, thus reducing the amount of incoming data when it’s mostly static. For affected proxies will require more resources than before. 10 Warning: The change affects the upgrade process to Zabbix 4.2. Please see the upgrade notes. Extended error messages Previously, in case of a preprocessing is collected only once for each datastore instead of one time per each hypervisor. Within this development the following new items have been added: • vmware.datastore.discovery[] • vmware.datastore

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . steps or complex logic. As an example, a Script item can be configured to make an HTTP call, then process the data received in the first step in some way, and pass transformed value to the second HTTP call It is now possible to choose the default language for the Zabbix frontend during the installation process. After the installation, the system default language can be changed in the Administration→General→GUI

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . for trigger expression debugging and internal actions. Expression debugging macros simplify the process of debugging trigger expressions: • {TRIGGER.EXPRESSION.EXPLAIN}, {TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} has been added to Zabbix server and proxy configuration files. You can use internal item zabbix[process,] to monitor ODBC pollers load. Runtime command transfer Zabbix server and proxy runtime

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1460 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . return a list of running processes/threads or summarized data grouped by process name. See also: • Zabbix agent item keys • Process parameters returned by proc.get item Extended VMware monitoring Multiple maximum supported version for TimescaleDB is now 2.9. Configuration import Previously, the import process would fail on a UUID mismatch of an importable entity (host group, item, graph, etc). For example

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557 3 Process configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . from the dashboard action menu for the currently opened dashboard. 10 A new Zabbix web service process should be installed to enable generation of scheduled reports. Currently scheduled reports generation instances as low as possible. To deal with host availability updates, a new availability manager process has been introduced. All processes queue host availability updates to the availability manager and