internal events, a much expanded set of macros is supported in notifications: • {ACTION.ID}, {ACTION.NAME} - return the ID or name of the action that delivered the notification. Supported in actions of all EVENT.RECOVERY.* macros. • {EVENT.RECOVERY.ID}, {EVENT.RECOVERY.DATE}, {EVENT.RECOVERY.TIME}, {EVENT.RECOVERY.STATUS}, {EVENT.RECOVERY.VALUE} - return the ID/date/time/verbal state or numeric state of (with macros not expanded) of an LLD rule. • {LLDRULE.ID}, {LLDRULE.NAME}, {LLDRULE.KEY}, {LLDRULE.DESCRIPTION}, {LLDRULE.STATE} - return the ID/name/key/description or verbal state of the low-level discovery

in map URLs macro {TRIGGER.ID} can be used. Additionally, 3 new macros have been added that also can be used in element URL fields: • {HOST.ID} • {HOSTGROUP.ID} • {MAP.ID} ** Grid selection saving breakdown of percentage usage of processor time: us - user time (float) sy - system time (float) id - idle time (float) wa - idle time during which the system had outstanding disk/NFS I/O request(s) monitoring SNMPv3 devices, make sure that msgAuthoritativeEngineID (also known as snmpEngineID or ”Engine ID”) is never shared by two devices. According to RFC 2571 (section 3.1.1.1) it must be unique for each

Windows eventlog filters 21 Windows eventlog entries now can be filtered by type, source and event ID on the agent side. 6.2.5 SSH and telnet checks Now SSH and telnet can be used for direct, agent-less multiple triggers with the same severity are assigned to the same map link, the one with the lowest ID takes precedence. 7.1.4 Unacknowledged trigger displaying in the dashboard It is now possible to DejaVu font upgraded from 2.31 to 2.32. • Screens can now be referenced on the frontend not only by id, but also by name. Adding GET parameter screenname will open the screen with that name, for example:

the new functionality, several macros are supported in the URL field: {HOST.CONN}, {HOST.DNS}, {HOST.ID}, {HOST.IP}, {HOST.HOST}, {HOST.NAME} and {$MACRO} user macro. 5.10.5 Responsible action shown in repository signing key (this has to be done only once): New repository or package signing key received: Key ID: 6F1385F1A0875A36 Key Name: home:zabbix OBS Project Key Fingerprint: breakdown of percentage usage of processor time: us - user time (float) sy - system time (float) id - idle time (float) wa - idle time during which the system had outstanding disk/NFS I/O request(s)

名 可 以 用 于 Host- Meta- dataItem 但 不 能 用 在 Host- nameItem 参 数 中。 例 如: \\1. 检 索 用 户’zabbix’ 的 ID. Alias=zabbix.userid:vfs.file.regexp[/etc/passwd,^zabbix:.:([0- 9]+)„„\1] 现 在 简 写 的 key zab- bix macros supported by Zabbix. Macro Supported in Description {ACTION.ID} → Notifications and commands → Internal notifications Numeric ID of the triggered action. Supported since 2.2.0. {ACTION.NAME} → notifications Date of the event that triggered an action. {EVENT.ID} → Notifications and commands → Internal notifications Numeric ID of the event that triggered an action. {EVENT.RECOVERY.DATE}→ Trigger-based

same Engine ID become unsupported in Zabbix leading to availability issues with these devices. To help troubleshoot such issues, information about SNMPv3 devices sharing the same Engine ID will now be be logged periodically by Zabbix server. Note that duplicate Engine ID detection works in each SNMP poller separately. Documentation link for each standard item Each standard item now has a direct link Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained by running ha_status) ha_set_failover_delay=delay

applies only to deleting history and trends of already deleted items. PidFile 否 tmp/zabbix_server.pid ID 文件名称。 PidFile no /tmp/zabbix_server.pid Name of PID file. ProxyConfigFrequency 否 -604800 600 abbix DebugLevel=3. This parameter is supported since Zabbix 1.8.2. PidFile 否 tmp/zabbix_server.pid ID 文件名称。 PidFile no /tmp/zabbix_proxy.pid Name of PID file. ProxyLocalBuffer 否 -720 roxy 将在本地保留数 据 N dataItem but not in Host- nameItem pa- ram- e- ters. Examples: 1. Re- triev- ing the ID of user ’zab- bix’. Alias=zabbix.userid:vfs.file.regexp[/etc/passwd,”^zabbix:.:([0- 9]+)”„„\1]

unknown values. 5.19 Miscellaneous improvements 5.19.1 Database changes The history_text.id and history_log.id fields were removed from the corresponding history tables. Those fields were redundant and 10.1 Frontend improvements • In Windows event log history events with a zero ”Event ID” now have their ”Event ID” displayed as ”0”. 10.1.1 Updated translations 10.2 Daemon improvements 11 What’s new about upgrading from previous Zabbix versions. Critical Database upgrade The history_text.id and history_log.id fields will be removed from the corresponding history tables during database upgrade. De-

applies only to deleting history and trends of already deleted items. PidFile 否 tmp/zabbix_server.pid ID 文件名称。 PidFile no /tmp/zabbix_server.pid Name of PID file. ProxyConfigFrequency 否 -604800 600 abbix DebugLevel=3. This parameter is supported since Zabbix 1.8.2. PidFile 否 tmp/zabbix_server.pid ID 文件名称。 PidFile no /tmp/zabbix_proxy.pid Name of PID file. ProxyLocalBuffer 否 -720 roxy 将在本地保留数 据 N dataItem but not in Host- nameItem pa- ram- e- ters. Examples: 1. Re- triev- ing the ID of user ’zab- bix’. Alias=zabbix.userid:vfs.file.regexp[/etc/passwd,”^zabbix:.:([0- 9]+)”„„\1]

HOST<1-9>}, {HOST.NAME<1-9>}, {HOST.CONN<1-9>}, {HOST.DNS<1-9>}, {HOST.IP<1-9>}, {HOST.PORT<1-9>}, {HOST.ID<1-9>} are now supported in event tag names and values, making it easier to specify host-related tags user has permissions to is now opened. Previously this choice was hard-coded and based on dashboard ID=1. • The height of a dashboard widget now can be no less than two rows so as to be able to display has been added to the request from frontend to server for script execution. This parameter takes the ID of session (authentication token) and it is used to check the user permissions to execute scripts