|
|
| |
Product / Documentation / Configuration / |
|
|
|
|
|
Actions |
Macros for messages
ZABBIX supports number of macros which may be used in notifications.
The following macros are supported:
| Macro | Definition |
| {DATE} | Current date in yyyy.mm.dd. |
| {EVENT.ID} | Numeric event ID which trigerred this action |
| {HOSTNAME} | Hostname of first item of the trigger which caused a notification. |
| {IPADDRESS} | IP address of first item of the trigger which caused a notification. |
| {STATUS} | See {TRIGGER.STATUS} |
| {TIME} | Current time in hh:mm.ss |
| {TRIGGER.ID} | Numeric trigger ID which trigerred this action |
| {TRIGGER.KEY} | Key of first item of the trigger which caused
a notification. |
| {TRIGGER.NAME} | Name (description) of the trigger. |
| {TRIGGER.SEVERITY} | Trigger severity. For example, "Disaster". |
| {TRIGGER.STATUS} | Trigger state. ON - if trigger is in TRUE state, OFF - if trigger is in FALSE state. |
| {hostname:key.func(param)} | Simple macros as used in trigger expressions. |
- Example 1. Subject: {TRIGGER.NAME}: {TRIGGER.STATUS}
Message subject will be replaced by something like:
"Processor load is too high on server zabbix.zabbix.com: ON"
- Example 2. Message: Processor load is: {zabbix.zabbix.com:system.cpu.load[,avg1].last(0)}
The message will be replaced by something like:
"Processor load is: 1.45"
|
|
|
|
| | © 2001-2008 by ZABBIX SIA. All rights reserved. Hosting is kindly provided by Clearcut Networks. | |