Alerts are fully customizable using ipMonitor Tokens:
Insert the following Tokens into your Alerts to obtain detailed date and time information.
| Date, Time and Formatting Tokens | ||
|---|---|---|
| Token Name | Description | Sample Return Value |
| %date% | Date (yy-mm-dd) | 04-03-02 |
| %dday% | Day (dd) | 17 |
| %mmon% | Month (mm) | 07 |
| %monthtext% | Month (full text) | January |
| %monthtext3% | Month (three letters) | Jan |
| %week% | Week in current month (one digit) | 1 |
| %weekday% | Weekday (one digit, Sunday = 0) | 4 |
| %weekdaytext% | Weekday (full text) | Friday |
| %weekdaytext3% | Weekday (three letters) | Fri |
| %year% | Year (yyyy) | 2004 |
| %yyear% | Year (yy) | 04 |
| %time% | Time (hh:mm::ss) based on 24-hour clock | 20:25:28 |
| %rfc822date% | Date/time in email format | Tue, 02 Mar 2004 20:25:28 -0500 |
| %% | Percent | % |
Insert the following Tokens into your Alerts to obtain Monitor-specific information, such as Monitor Name, Type, Duration of Monitor failure, etc.
| Monitor Tokens | ||
|---|---|---|
| Token Name | Description | Sample Return Value |
| %monitorid% | Monitor ID | 589478484027 |
| %monitorname% | Monitor Name | HTTP - Website |
| %monitortype% | Monitor Type | ado |
| %monitoravail% | Monitor available time (%) | 99.95 |
| %monitorcoverage% | Monitor coverage time (secs) | 174697 |
| %monitorfailures% | Monitor Failures | 0 |
| %monitorcriticals% | Monitor Failures - Critical | 0 |
| %monitorcritstoalert% | Critical Alert | 3 |
| %monitorstatus% | Last Monitor Status | could not obtain an IP address for the device; |
| %monitorlastrun% | Date / Time Monitor Last Run | Sun, 21 Dec 2003 17:29:10 -500 |
| %monitordowndate% | Date / Time Monitor Reported Failure | Sun, 21 Dec 2003 17:29:10 -500 |
| %monitormaxtest% | Maximum Test Duration (secs) | 300 |
| %monitoralertmax% | Maximum Alerts to Send | 3 |
| %monitoralertno% | Alert Number | 2 |
| %monitoralertssent% | Number of Alerts Sent | 1 |
| %monitordownlength% | Duration of Monitor Failure | 0.80 minutes |
| %monitoruplength% | Total Monitor Up Time | 2 days, 2 hours, 2.70 min |
| %monitorstate% | Current Monitor State (text) | down |
| %monitorstatenum% | Current Monitor State (number) | 1 |
| %monitortestup% | Delay Between Tests While Up (secs) | 300 |
| %monitortestwarn% | Delay Between Tests While Warn (secs) | 300 |
| %monitortestdown% | Delay Between Tests While Down (secs) | 300 |
| %monitortestlost% | Delay Between Tests While Lost (secs) | 300 |
| %monitor[addr]% %monitor[port]% %monitor[target]% %monitor[info/logfile]% |
Monitor Configuration Data from the |
10.25.0.10 53 INTRANETSRV Security |
| %monitortag[...]% | Value of Tag Name Specified | Brian Smith, cell: 555-9876 |
Insert the following Tokens into your Alerts to obtain Alert-specific information, such as Profile and Alert Name, information found in custom Tags, etc.
| Alert and Profile Tokens | ||
|---|---|---|
| Token Name | Description | Sample Return Value |
| %profilename% | Alert is a Member of this Profile | Night Crew |
| %alertname% | Alert Name | Internal Helpdesk - Simple Email |
| %alert[sendmail/emailto]% %alert[emailfrom]% |
Alert Configuration Data from the |
admin@xyzcompany.com ipm7@xyzcompany.com |
| %alerttag[...]% | Value of Tag Name Specified | http://intranet. xyzcompany.com/ recovery.aspx |
Insert the following Tokens into your Alerts to obtain system-specific information, such as the ipMonitor Server Name, CPU utilization by the ipMonitor process, available drive space, etc.
| System Tokens | ||
|---|---|---|
| Token Name | Description | Sample Return Value |
| %instancename% | ipMonitor Server Name | ipMonitor Server [PRIMARY] |
| %processcpu% | ipMonitor CPU Utilization | 56.78 seconds |
| %processuptime% | ipMonitor Uptime | 3.81 hours |
| %processavg% | ipMonitor CPU Load | 0.40% |
| %sysmemavail% | Physical Memory Available | 359.83 MB |
| %sysswapavail% | Commit Memory Available | 535.78 MB |
| %ipmdriveavail% | ipMonitor Drive-Space Available | 26.15 GB |
%monitor[...]% may contain other values in the
%monitortag[...]% will display the value of a custom Tag for the specific Monitor. The Name of the Tag is entered within the square brackets [ ].
%alert[...]% may contain other values in the
%alerttag[...]% will display the value of a custom Tag for the specific Alert. The Name of the Tag is entered within the square brackets [ ].
The Content Generator has access to %monitor[...]% and %monitortag[...]%, but does not have access to %alert[...]% or %alerttag[...]%.
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
< Back
![]()
Last Updated: March 30, 2007 | What did you think of this topic?