See also ZBXNEXT-384.

Any chance of getting it coded? It would be very usefull for me! TRIGGER_DURATION or something like that. Thank you for zabbix!

Just going to throw it out there, this would indeed be a killer feature for automated downtime calculations based on the first action firing.

I monitor web scenarios and have a custom action for notifications of these. In the recovery message I included the macro EVENT.AGE which then tells me how long my scenario had failed. Not exactly what is requested here but sounds so similar that it might be useful for some.

I think it should be implemented as macro {EVENT.DURATION}, which will return event duration (obviously). The macro will be used in all contexts currently supported by existing macro {EVENT.AGE}, except Discovery and Autoregistration notifications. Output format will be also identical to {EVENT.AGE}.

Mini SPEC:

Add support new macro {EVENT.DURATION} for macros with following types:

• MACRO_TYPE_MESSAGE_NORMAL
• MACRO_TYPE_MESSAGE_RECOVERY
• MACRO_TYPE_MESSAGE_ACK

Output format will be also identical to {EVENT.AGE}.
Scenarios of the macro substitution

source	object	status
EVENT_SOURCE_TRIGGERS
EVENT_SOURCE_INTERNAL	EVENT_OBJECT_TRIGGER
EVENT_SOURCE_INTERNAL	EVENT_OBJECT_ITEM
EVENT_SOURCE_INTERNAL	EVENT_OBJECT_LLDRULE
EVENT_SOURCE_DISCOVERY
EVENT_SOURCE_AUTOREGISTRATION

The recovery message template:

Problem has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}
Problem name: {EVENT.NAME}
Problem duration: {EVENT.DURATION} 
Host: {HOST.NAME}
Severity: {EVENT.SEVERITY}
Original problem ID: {EVENT.ID}
{TRIGGER.URL}

Available in

• 5.0.0alpha4(master) 2f1405e866c, 309e90a6ad7

Documentation updated:

• What's new in 5.0
• Supported macros