in one operation. 5.25.7 Multiple timer processes Zabbix server daemon will support parallel processing of time-based functions. A user can specify the number of timer processes in the new StartTimers listener #1 [waiting for connection] zabbix22 4741 4738 0 14:55 ? 00:00:00 zabbix_agentd: listener #2 [processing request] The commandline of the main process is shown unchanged (in previous versions it was displaying mode • Zabbix proxy value collection, network discovery and active agent autoregistration data processing Added indexes on child-table columns having foreign key constraints Such indexes were created

button has been added to the web scenario configuration form. 5.7 Optional SNMP bulk requests Bulk processing of SNMP requests was first introduced in Zabbix 2.2.3. While providing benefits in terms of reduced number of devices that did not respond to these requests as expected. As a result, SNMP bulk processing has been made optional in Zabbix 2.4.0. Enabled by default, it can be disabled per interface in with problems, as before, a red square icon is displayed in this column. 5.10.14 Changing uploaded image type disallowed The type of uploaded images previously could be freely changed from Icon to Background

polling discovery, history and auto-registration data from that proxy. Apart from better messages processing of historical data from proxies and active agents is not affected. Log file messages containing Portuguese (Brazil) 6.2 Daemon improvements 6.2.1 VMware monitoring optimisations The VMware data processing and storage was changed, resulting in less time VMware cache is locked and also reducing the size Russian • Turkish Enabled Turkish translation to be displayed by default. Processing low-level discovery (LLD) LLD rule processing has been modified so multiple values for the same LLD rule are not processed

trigger prototype cannot depend on a trigger from a template. 5.9.1 Performance improvements The processing of trigger prototypes has been optimized by reducing the number of SQL statements. As a result seem to have any users. 5.20.15 History cache improvements History cache will better handle the processing of a large number of values (100 and more values per item) coming from a low number of items (100 caching Actions and action conditions are now stored in configuration cache, improving action processing performance. 23 5.21 Item changes/improvements A new proc.cpu.util item has been added to monitor

needed for the dependent item from 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 (like SMS and e-mail) with the email waiting for the SMS to be sent. In the new version, parallel processing of alerts is implemented. There is a new alert manager process that can distribute alerts to several by one trigger are processed sequentially. There are other related changes: • Three new alert processing options available in the media type configuration: Concurrent sessions, Attempts and Retry interval:

possible to enable Advanced labels feature per map and choose map element label per element type - image, trigger, host, host group and map. ** Displaying hosts from a host group ** For host group element PHP option max_upload_filesize limit. Now Zabbix shows a warning when uploading a too large XML or image file. 5.2.22 Improved configuration wizard For configuration wizard requirements step, Recommended added optional suppressing of processing of older data in log[], logrt[] and eventlog[] additional parameter mode controls this: • all (default) • skip (skipping processing of older data) 16 5.3.2.2

Low-level discovery Separate processing for low-level discovery Processing low-level discovery rules has been split from data gathering processes into its own processing. See: Daemon improvements. Expected key. Any new native discovery checks will use the new syntax without the ”data” elements. When processing a low-level discovery value first the root is located (array at $. or $.data). While the ”data” supported macros. Daemons Separate processing for low-level discovery Processing low-level discovery rules has been split from data gathering processes into its own processing, consisting of a config- urable

widget uses vector technique to draw the image and serves as a platform for multiple new visualization features that were not available using the existing image drawing approach. For more information using a name: prefix before the value. Triggers Time triggers processed by history syncers The processing of time-based trigger functions such as nodata(), date(), dayofmonth(), dayofweek(), time() and recalculated at the same time, creating peak loads every 30 seconds, now the time- based trigger processing is evenly spread within those 30 seconds. The output of history syncer and timer processes has

applications. 27 Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load off of the server. encryption - support of encrypted communications between Zabbix components acknowledge problem, check item value now, remote command functionality) • timer - timer for processing maintenances • trapper - trapper for active checks, traps, proxy communication • unreachable The agent gathers operational information locally and reports data to Zabbix server for further processing. In case of failures (such as a hard disk running full or a crashed service process), Zabbix server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Main principles of Zabbix development • be user friendly • keep things simple • use as few processing resources as possible • react fast • document every aspect of the software 3 Installation and editing Zabbix supports network maps where monitored environment can be laid out on a background image to provide user friendly overview. In previous versions, editing such network maps was not easy -