Alerts are fully customizable using ipMonitor Tokens. Simply click on any number of Tokens in the convenient Token selector, and when an Alert is executed, the Tokens will be replaced with dynamic content.
Tokens are grouped into three different categories:
| Token | |
| Description | Sample Value Returned |
| %monitorid% | |
| Monitor ID | 589478484027 |
| %monitordownlength% | |
| Duration of Monitor Failure | 0.80 minutes |
| %monitortag[contact]% | |
| Value of Tag Name Specified: Custom Data for Specific Monitor |
Brian Smith, cell: 555-9876 |
Note: %monitortag[...]% will display the value of a user created Tag for the specific Monitor. The Name of the Tag is entered in the [ ].
| Token | |
| Description | Sample Value Returned |
| %alertname% | |
| Alert Name | Internal Helpdesk - Simple Email |
| %rfc822date% | |
| Date - RFC 822 Format | Tue, 02 Mar 2004 20:25:28 -0500 |
| %alerttag[emerg_contact]% | |
| Value of Tag Name Specified: Custom Data for Specific Alert |
Brian Smith, cell: 555-9876 |
Note: %alerttag[...]% will display the value of a user created Tag for the specific Alert. The Name of the Tag is entered in the [ ].
| Token | |
| Description | Sample Value Returned |
| %instancename% | |
| ipMonitor Instance Name | ipMonitor Server [PRIMARY] |
| %processavg% | |
| ipMonitor 7 CPU Load | 0.40% |
| %ipmdriveavail% | |
| ipMonitor Drive Space Available | 26.15 GB |
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
< Back
![]()
Last Updated: April 25, 2006 | What did you think of this topic?