introduces new and updated features of Zabbix 4.2. Extended item value preprocessing JavaScript It is now possible to apply preprocessing to item value or low-level discovery values using JavaScript. The the code block. 7 Validation and throttling rules New options have been added to item value preprocessing focusing on validation and throttling. New validation options such as defining the acceptable another new feature. For example, a JSON object may contain a field ”error”. If the field exists preprocessing is able to extract its value and set it as an error message for the item. 8 Throttling rules

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285 6 Preprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Thus it may be used as a master item gathering all required metrics in one system call. JSONPath preprocessing can be used in dependent items to extract individual values from this master item. The new item new item is capable of returning the entire response of the query, formatted as JSON. JSONPath preprocessing can be used to point to more specific values in the returned JSON. The new item may be used

test the preprocessing steps. In fact, the item testing form is an extension of the preprocessing testing form already known in recent Zabbix versions. So if previously you could test preprocessing steps a hypothetical input value, now it is also possible to test preprocessing against a real test value just received. To test the preprocessing steps against the real value, click on Get value and 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 functionality

becoming unsupported, now it is possible to use a new preprocessing rule called ”Check for not supported value” to handle this situation. This preprocessing rule has standard Custom on fail options allowing in triggers) • set another error message 10 This preprocessing step can be used only once and it makes sense to have it as the first preprocessing step. The main use cases for this functionality are |<| |<| |-| |<| Informative tabs allow to debug problems easier, for example, when an item has preprocessing steps defined they are now clearly indicated with a number even when the tab is not opened:

Additional JavaScript objects. XML to JSON preprocessing option New option XML to JSON has been added in item preprocessing and low-level discovery preprocessing. Strong encryption protocols for SNMPv3 users with the Super admin role type. Diagnostic information Diagnostic information about preprocessing has been improved to include the oldest values in queue and the totals to include done, queued object. Now the item returns a normal JSON containing an array, thus allowing to apply item value preprocessing steps directly to the returned data without additional workarounds. Old JSON format New JSON

located under the Key parameter on the primary Item tab and is duplicated on the Preprocessing tab if at least one preprocessing step is specified. If Zabbix detects a possible mismatch of the selected type processing for Prometheus metrics Bulk processing of dependent items has been introduced in the preprocessing queue to improve the performance of retrieving Prometheus metrics. See Prometheus checks for monitoring. All encoding formats supported by libcurl are supported. Preprocessing Prometheus query language Zabbix Prometheus preprocessing query language now supports two additional label matching operators:

configuration cache synchronization has been added for hosts, host tags, items, item tags, item preprocessing, trig- gers, trigger tags and functions to lessen synchronization time and database load when change has been implemented to simplify further processing of the returned JSON (for example, in preprocessing steps or LLD macros). Tag reading from VMware VMware items reporting various VMware tags (e supported version for PHP is now 8.2. Limits for JavaScript objects in preprocessing The following limits for JavaScript objects in preprocessing have been intro- duced: • The total size of all messages that

helper window from the item configuration form (click on Select next to the item key field). Preprocessing Advanced root-cause handling for unsupported item state Error handling in case of a failure to error message can be ”mapped” to a more general case to be matched for and handled by a further preprocessing step, or some intermittent (e.g., network connectivity) issue can be handled differently to a a definite failure to acquire the item value. Multiple Check for not supported value preprocessing steps can now be added. Note that there can be only one ”any error” matching step at the end of the

3.6.1.2.1.2.2.1.3] returns a multi-line list of interface names and types. Using the Zabbix preprocessing options, the response of this item may be used to discover interfaces, create discovered items dependent item prototypes of the walk[] master item. To make this functionality possible, two new preprocessing steps have been added: • SNMP walk value - extract and format SNMP walk value by the specified is Zabbix own way of combining multiple SNMP requests. See also: • SNMP agent checks • Item preprocessing • SNMP OID discovery Notification macros in alert scripts Alert script parameters now support

value for the master item automatically populates the values of the dependent items. Zabbix preprocessing options can be used to extract the part that is needed for the dependent item from the master more distinct from recovery notifications in the message subject 7 Item value preprocessing When it comes to preprocessing item values before storing them in the database, Zabbix already had several options new version, all item value preprocessing is brought together and put in the hands of the user under a new Preprocessing tab in item configuration. 7.1 New preprocessing options Several new options