replace them with some default value or simply replace them with a human-readable error message. Extracting an error message provided in incoming data is another new feature. For example, a JSON object may contain ”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 allow to process value only if it is changed, thus reducing the handling option, e.g.: • discard the value • set to a specified value • set a specified error message Testing preprocessing steps As new item preprocessing steps are being added the preprocessing pipeline

for each media type It is now possible to specify default message templates for each event type when defining media types. Thus default message editing no longer takes place when configuring action operations displayed (or N problems selected if there is more than one problem) • Size of the problem update message has been increased from 256 to 2048 characters • It is now possible to unacknowledge problems (see not be resolved. Webhooks The MS Teams webhook now supports custom fields and custom buttons in message cards. Regular expression support in user macro context In addition to static strings, regular

sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem escalation scenarios. New message templates only numeric, but also text, log, and character types of information. Bulk processing for Prometheus metrics Bulk processing of dependent items has been introduced in the preprocessing queue to improve Result processing for Prometheus pattern A Prometheus pattern step in the preprocessing can produce a result where multiple lines are matched. To handle this situation, a new result processing parameter

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:

preprocessing steps. In a typical use case of custom error handling, data can be skipped if an error message is found. More options for LLD rule preprocessing More preprocessing options have been added to Cannot support audio notification notice “Cannot support notification audio for this device.” message will be displayed when notification sounds on the device cannot be played. Monospaced fonts in By default this option is unchecked and before it is possible to mark this checkbox a warning message is displayed that all inherited entities may be lost as a result. Zabbix agent 2 (Windows) Zabbix

may also use the new ”Event name” parameter in trigger configuration to build a meaningful alert message, for example to receive something like: "Load of Exchange server increased by 24% in July (0.69) The new expression macros and new macro functions (’fmttime’ and ’fmtnum’) are used to build this message. For more details on configuring the event name, see a trigger configuration example. See also: this case the item becomes supported and the value can be used 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

will be ”0”; otherwise, the component will exit with non-zero exit code and a corresponding error message. Warnings (e.g., in case of a deprecated parameter) will not affect successful exit code. Stream either to discard the value, set a specified value or set a specified error message. 13 It is now possible to match the error message to a regular expression. If the error matches (or does not match) it is is possible to specify how the error case should be processed. For example, a specific error message can be ”mapped” to a more general case to be matched for and handled by a further preprocessing step

to return HMAC hash: • hmac('',key,string) This is useful for cases when hash-based message authentication code (HMAC) is required for signing requests. MD5 and SHA256 hash types are supported instead of vm.customattribute. This formatting change has been implemented to simplify further processing of the returned JSON (for example, in preprocessing steps or LLD macros). Tag reading from VMware and the Delete missing option for the specific entity is marked. Due to this change, the warning message when marking the Delete missing option for template linkage will no longer be displayed. Query separate

been implemented allowing to cache the result of calculated trend functions. Zabbix server, when processing trend functions, will check the trend cache for the cached result. In case of failure the server If the version of the database used is below or above supported range a warning message will be displayed. The message will be visible only to users with the Super admin role type. Diagnostic information has been improved to include the oldest values in queue and the totals to include done, queued, processing and pending. Web scenario fields The maximum field size has been increased from 255 to 2000 characters

notification recipients, now you can also filter records by actions, media types, status, or by the message/remote command content. These filtering options can also be configured for the Action log widget commands. 24 media - a means of delivering notifications; delivery channel. notification - a message about some event sent to a user via the chosen media channel. remote command - a pre-defined command data. Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load from the server. Zabbix agent - a process deployed on monitoring targets to actively monitor