available for dealing with fast-growing log files. The key issue with such files is the enormous number of messages, which are written to the log files in certain situations. As all new lines must be Zabbix and the matching lines sent to Zabbix server, it may result both in serious delays and a large number of identical messages sent and stored in the database. To deal with these issues there are two recent ones. • log.count and logrt.count - two new agent items that count the number of matched lines and return that number instead of the lines themselves. 5.8 Easier trigger hysteresis Trigger hysteresis

send problem notifications. Alerts were sent out one by one and, in large environments with a large number of events happening in close succession, delays with alerts could occur. Similarly, delays could needed. Media types are processed in parallel. The maximum number of concurrent sessions is configurable per media type, but the total number of alerter processes on server can only be limited by the new setting in map properties has been reworked into a three-way choice. The new option here is called Number of problems and expand the most critical one. This option is related to the multiple trigger support

called Zabbix agent 2. Some of the goals set when devel- oping the new agent 2 were to: • reduce the number of TCP connections • have greater check concurrency • be easily extendible with plugins • be a as one aggregated value: See also: Aggregation in graphs Dependent item limit raised The maximum number of allowed dependent items for one master item has been raised from 999 to 29999. Kerberos authentication required values in the returned JSON. Low-level discovery Low-level discovery of block devices Low-level discovery of block devices and their type is supported using a new built-in discovery key: vfs.dev

instances. As each history poller requires a database connection, it is recommended to keep the number of instances as low as possible. To deal with host availability updates, a new availability manager variables and post fields. 7 What’s new in Zabbix 5.4.2 Media types In media types, the maximum number of attempts to send an alert has been increased from 10 to 100; the maximum attempt interval has Zabbix agent (Unix/Windows) configuration. This optional parameter can be used to specify the maximum number of pending connections in the TCP queue. 10 What’s new in Zabbix 5.4.5 New templates New template

- a non-empty JavaScript code block. Clicking in the parameter field or on the view/edit button next to the parameter field will open a window for entering the code block. 7 Validation and throttling can be tested together using the new Test or Test all steps buttons respectively in the Actions block. See also: Testing preprocessing steps. Preprocessing support on Zabbix proxy For hosts monitored of a preprocessing error, the item would become unsupported and the error message would report the number of the failed preprocessing step along with the error description. Item preprocessing step #

been upped from 7.2.0 to 7.2.5. 12 Informative tabs Tabs in many frontend forms now indicate the number of defined elements or if the functionality is enabled. To illustrate let’s compare a host configuration for example, when an item has preprocessing steps defined they are now clearly indicated with a number even when the tab is not opened: Informative tabs have been added to the configuration forms for: – includes Working hours field (used to be on a separate page); – contains new parameters: Max number of columns and rows in overview tables, Show technical errors, Max history display period, Default

--runtime-control perform administrative functions -h --help give this help -V --version display version number Examples of running Zabbix server with command line parameters: shell> zabbix_server -c /usr/l specified type (e.g., poller) See all server process types. process type,N - Process type and number (e.g., poller,3) pid - Process identifier (1 to 65535). For larger values specify target as ’process stdout) • ha_remove_node=target - remove an HA node identified by its - number of the node in the list (the number can be obtained from the output of running ha_status), e.g.: zabbix_server -R

functions. Change count A new history function changecount() has been added allowing to count the number of changes between adjacent values. The function supports three different modes for counting all decreases, or only increases. As an example, it can be used to track changes in the number of users or the number of system uptime decreases. Entity count New functions have been added to simplify the functions. Aggregate functions: • count - total number of values in an array returned by a foreach function (returns an integer); • item_count - total number of currently enabled items that match filter

Latest data section) • Problems (number of open problems and a link to Problems section) • Graphs (number of graphs and a link to Graphs section) • Screens (number of screens and a link to Screens section) section) • Web scenarios (number of web scenarios and a link to Web section) Links in the list above provide a convenient way to view corresponding page with more details about the given host. Users regular files and links. Support for more file types has been added including directories, sockets, block devices, character devices, etc. Several file types to include can be specified in the second parameter

in terms of reduced network traffic and load on SNMP devices, it also encountered problems with a number of devices that did not respond to these requests as expected. As a result, SNMP bulk processing on installations with a lot of triggers. Now the setting is in force and can be used to limit the number of records displayed in one page. • Templates listed in the host configuration have been made clickable process selection. A target process can be selected by specifying PID or process type and process number. 5.13 Item changes/improvements zabbix[host„maintenance] is a new internal item that returns the