Custom message and "Disk read/write request responses are too high"

[catkins]

Our Zabbix 5.0 custom message is

Host: {HOST.NAME}
Severity: {EVENT.SEVERITY}
Problem started at {EVENT.TIME} on {EVENT.DATE}
Problem name: {EVENT.NAME}
Item: {ITEM.NAME}
Item value: {ITEM.VALUE}
Original problem ID: {EVENT.ID}

That works well for most triggers but is misleading for "Template OS Linux by Zabbix agent active"'s "Disk read/write request responses are too high" trigger. Example

Host: storage4.iciti.av
Severity: Warning
Problem started at 03:40:47 on 2021.08.28
Problem name: sdc: Disk read/write request responses are too high (read > 20 ms for 15m or write > 20 ms for 15m)
Item: sdc: Disk read request avg waiting time (r_await)
Item value: 1.74 ms Original problem ID: 319756

It was the write request response which was too high but as shown the message showed the read request value

How can we modify the custom message so it also shows the write request value?

I guess we could add {ITEM.VALUE2} but that would result in an empty value for all those triggers which have only one item

[catkins]

Thanks Cyber, that worked well. The final custom message definition was

Host: {HOST.NAME}
Severity: {EVENT.SEVERITY}
Problem started at {EVENT.TIME} on {EVENT.DATE}
Problem name: {EVENT.NAME}
Current value(s): {EVENT.OPDATA}
Original problem ID: {EVENT.ID}

And recovery

Recovered at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}
Started at {EVENT.TIME} on {EVENT.DATE}
Problem name: {EVENT.NAME}
Current value(s): {EVENT.OPDATA}
Original problem ID: {EVENT.ID}

That generated, example

Host: cc1.example.com
Severity: Warning
Problem started at 14:36:03 on 2021.08.31
Problem name: Interface Gi1/0/12(edge1-pulse): High error rate (> 2 for 5m)
Current value(s): errors in: 0, errors out: 0
Original problem ID: 428315

Reason for "Current value(s):" is because, as in the example above, the values shown by {EVENT.OPDATA} can be zero while the trigger fired on a non-zero time average. At first I had "Value(s):" but that was misleading because the values displayed were not what had fired the trigger