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

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

8 JSON protocol for passive agent checks A JSON-based protocol for passive agent checks has been implemented. For compatibility with older agents, a failover to the old plaintext protocol has been Zabbix will cache the interface as old protocol and retry the check by sending only the plaintext item key. Zabbix get can now be run with a new option -P --protocol where ”value” is either: • auto auto - connect using JSON protocol, fall back and retry with plaintext protocol (default); • json - connect using JSON protocol key; • plaintext - connect using plaintext protocol where just the item key

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 Zabbix. Databases Support for MariaDB 10.6.X has been added. Handling large proxy configuration Protocol has been improved to support Zabbix proxy configuration of size up to 16 GB. Additionally performance improved by freeing uncompressed data as fast as possible and compressing before connection. See also protocol header information. Items • Zabbix agent 2 items proc.num, proc.cpu.utilization, proc.mem have

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 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 remote commands. 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

details (e.g. the Updated: hh:mm:ss message about the time they were updated), achieving a much cleaner look of the dashboards. Note that: – In the Problems widget the message ”N of M problems are shown” will been introduced allowing data polling using the HTTP/HTTPS protocol. Trapping is also possible using Zabbix sender or Zabbix sender protocol. For more details see HTTP agent item type. New templates about each activity. • Previously in event details there were separate blocks for acknowledgments, message and remote command actions. Now all activities on the problem are displayed in one block and symbolic

. . . . . . . 83 3.3 The kernel message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 3.4 The system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 7.2 GUI communication protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 7 accounts can be created with adduser(8) by root. The system starts with the greeting message stored in ”/etc/motd” (Message Of The Day) and presents a command prompt. Debian GNU/Linux 11 foo tty1 foo login:

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 size has been increased for the following fields: – Item preprocessing parameters – Media type message • The default language of Zabbix web interface has been changed from British to American English 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

is now possible to stream item values and events from Zabbix to external systems over HTTP (see protocol details). The tag filter can be used to stream subsets of item values or events. Warning: This a Zabbix agent configuration file default value is changed to 5 seconds (previously 120). JSON protocol for active agent checks has been updated to include config_revision and session ID. For more information 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

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