way of defining trigger hysteresis by introducing an optional second trigger expression called ’recovery expression’ where you can separately define the conditions that have to be met for the trigger to generated. You can use the problem expression as basis (then it works the same way as before), the recovery expression as basis, or even select ’None’ in which case the trigger will always remain in problem Trigger hysteresis 5.9 Recovery operations Being notified on problem recovery has become easier in Zabbix. If previously there was the slightly confusing concept of a special ”Recovery message” or the possibility

ACTION} added – {EVENT.SEVERITY} added – {EVENT.NSEVERITY} added • Default messages for operations, recovery operations and update operations have been changed to reflect the updated macros New graph widget in the ’events’ and ’problem’ tables at the moment when an event is generated for a problem or recovery. Zabbix frontend can search and query the respective tables directly. This change leads to a better that for internal events the name contains an error message why an object changed its state; upon recovery no name is used. For discovery and auto-registration events no name is used. A new {EVENT.NAME}

indicated using the {HOST.NAME} macro • Problem notifications have been made more distinct from recovery notifications in the message subject 7 Item value preprocessing When it comes to preprocessing is not associated with a problem in any way. This means that if an event is either a problem or recovery event, it will not be deleted until the related problem record is removed. Additionally, the housekeeper Template Module Interfaces SNMPv2) leads to a problem resolving prematurely. Fixed by adding a recovery expression disallowing this in 3.4.9. For details, see: ZBX-13278. Known issues for 3.4.0 - 3

been added, similar to other actions in Zabbix. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending service actions support problem escalation scenarios. New message templates Service, Service recovery, and Service update have been added to media types and should be defined to enable correct sending {TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} - resolve to a partially evaluated trigger or recovery expression, where only item-based functions are applied; • {FUNCTION.VALUE<1-9>}, {FUNCTION.RECOVERY.VALUE<1-9>} -

first rendering time of the notification. • The Display OK triggers for setting is now applied to recovery type notifications. That becomes relevant if it is shorter than the regular problem notification containing the message body and title in response, if the client receives the same notification ID. • Recovery of a crashed tab is implemented. Any tab that is still able to execute JavaStript will detect a Templates you can import it manually into Zabbix. Macros A new {EVENT.RECOVERY.NAME} macro is supported, returning the recovery event name. {TRIGGER.ID} macro is now supported in trigger tag values.

per second. For each recovered event, an event_recovery record is created. Normally most of the events will be recovered so we can assume one event_recovery record per event. That means additional 80 bytes service - Oracle service name. oracle.fra.stats[connString,,,] Fast Recovery Area (FRA) statistics. JSON object connString - URI or session name. user, password - Oracle pgsql.dbstat.conflicts.rate[”{#DBNAME}”] - the number of queries canceled due to conflicts with recovery in this database (the conflicts occur only on standby servers). pgsql.dbstat.temp_files.rate[”{#DBNAME}”]

duration of an event. • {EVENT.TAGSJSON} and {EVENT.RECOVERY.TAGSJSON} macros will resolve to a JSON array containing event tag objects or recovery event tag objects. For more details, see Macros supported correlation conditions • Problem update screen • Action operation details – in the Operations, Recovery operations and Update operations tabs • Maintenance period details – in the Periods tab • Discovery per second. For each recovered event an event_recovery record is created. Normally most of events will be recovered so we can assume one event_recovery record per event. That means additional 80 bytes

per second. For each recovered event, an event_recovery record is created. Normally most of the events will be recovered so we can assume one event_recovery record per event. That means additional 80 bytes pgsql.dbstat.conflicts.rate[”{#DBNAME}”] - the number of queries canceled due to conflicts with recovery in this database (the conflicts occur only on standby servers). pgsql.dbstat.temp_files.rate[”{#DBNAME}”] pgsql.dbstat.sum.conflicts - database statistics about query cancels due to conflict with recovery on standby servers. pgsql.dbstat.sum.deadlocks - the number of deadlocks detected in this

per second. For each recovered event an event_recovery record is created. Normally most of events will be recovered so we can assume one event_recovery record per event. That means additional 80 bytes pgsql.dbstat.conflicts.rate[”{#DBNAME}”] - the number of queries canceled due to conflicts with recovery in this database (the conflicts occur only on standby servers). pgsql.dbstat.temp_files.rate[”{#DBNAME}”] pgsql.dbstat.sum.conflicts - database statistics about query cancels due to conflict with recovery on standby servers. pgsql.dbstat.sum.deadlocks - the number of deadlocks detected in this

Now, to achieve better readability, triggers that are based on one host item only in problem and recovery expression are listed within the tags of the respective host item. Additionally the expression area fonts have been changed to monospace in the following locations: • Trigger expression and recovery expression field • Executed script field of SSH/Telnet agent items • Formula field of calculated called item_rtdata. 6 What’s new in Zabbix 4.4.1 Macros A new {EVENT.RECOVERY.NAME} macro is supported, returning the recovery event name. {TRIGGER.ID} macro is now supported in trigger tag values.