4 Using macros in messages

Overview

In message subjects and message text you can use macros for more efficient problem reporting.

In addition to a number of built-in macros, user macros and expression macros are also supported. A full list of macros supported by Zabbix is available.

Examples

Examples here illustrate how you can use macros in messages.

Example 1

Message subject:

  1. Problem: {TRIGGER.NAME}

When you receive the message, the message subject will be replaced by something like:

  1. Problem: Processor load is too high on Zabbix server
Example 2

Message:

  1. Processor load is: {?last(/zabbix.zabbix.com/system.cpu.load[,avg1])}

When you receive the message, the message will be replaced by something like:

  1. Processor load is: 1.45
Example 3

Message:

  1. Latest value: {?last(/{HOST.HOST}/{ITEM.KEY})}
  2. MAX for 15 minutes: {?max(/{HOST.HOST}/{ITEM.KEY},15m)}
  3. MIN for 15 minutes: {?min(/{HOST.HOST}/{ITEM.KEY},15m)}

When you receive the message, the message will be replaced by something like:

  1. Latest value: 1.45
  2. MAX for 15 minutes: 2.33
  3. MIN for 15 minutes: 1.01
Example 4

Message:

  1. http://<server_ip_or_name>/zabbix/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID}

When you receive the message, it will contain a link to the Event details page, which provides information about the event, its trigger, and a list of latest events generated by the same trigger.

Example 5

Informing about values from several hosts in a trigger expression.

Message:

  1. Problem name: {TRIGGER.NAME}
  2. Trigger expression: {TRIGGER.EXPRESSION}
  3. 1. Item value on {HOST.NAME1}: {ITEM.VALUE1} ({ITEM.NAME1})
  4. 2. Item value on {HOST.NAME2}: {ITEM.VALUE2} ({ITEM.NAME2})

When you receive the message, the message will be replaced by something like:

  1. Problem name: Processor load is too high on a local host
  2. Trigger expression: last(/Myhost/system.cpu.load[percpu,avg1])>5 or last(/Myotherhost/system.cpu.load[percpu,avg1])>5
  3. 1. Item value on Myhost: 0.83 (Processor load (1 min average per core))
  4. 2. Item value on Myotherhost: 5.125 (Processor load (1 min average per core))
Example 6

Receiving details of both the problem event and recovery event in a recovery message:

Message:

  1. Problem:
  2. Event ID: {EVENT.ID}
  3. Event value: {EVENT.VALUE}
  4. Event status: {EVENT.STATUS}
  5. Event time: {EVENT.TIME}
  6. Event date: {EVENT.DATE}
  7. Event age: {EVENT.AGE}
  8. Event acknowledgment: {EVENT.ACK.STATUS}
  9. Event update history: {EVENT.UPDATE.HISTORY}
  10. Recovery:
  11. Event ID: {EVENT.RECOVERY.ID}
  12. Event value: {EVENT.RECOVERY.VALUE}
  13. Event status: {EVENT.RECOVERY.STATUS}
  14. Event time: {EVENT.RECOVERY.TIME}
  15. Event date: {EVENT.RECOVERY.DATE}
  16. Operational data: {EVENT.OPDATA}

When you receive the message, the macros will be replaced by something like:

  1. Problem:
  2. Event ID: 21874
  3. Event value: 1
  4. Event status: PROBLEM
  5. Event time: 13:04:30
  6. Event date: 2018.01.02
  7. Event age: 5m
  8. Event acknowledgment: Yes
  9. Event update history: 2018.01.02 13:05:51 "John Smith (Admin)"
  10. Actions: acknowledged.
  11. Recovery:
  12. Event ID: 21896
  13. Event value: 0
  14. Event status: OK
  15. Event time: 13:10:07
  16. Event date: 2018.01.02
  17. Operational data: Current value is 0.83

Separate notification macros for the original problem event and recovery event are supported since Zabbix 2.2.0.