Alert Templates can be found/created in the main menu under Configure > Alert Templates.
Templates define the look and feel of the alert messages. For example, technical users’ messages could have links to network traceroutes or even snapshots of the download that caused the alert.
The Alert Template editor allows you to input static and dynamic variables to customize the alert for the intended recipient. The dynamic variables can be used in both the subject and the body of the alert emails. For example, a device name, error code, a response time can be added to the message. This can help troubleshoot the errors that trigger an alert.
Check the available static variables below:
<%Contact_Full_Name%> <%Contact_Org_Name%> <%Contact_Title_Name%> <%Site_Name%> <%Monitor_Datetime%> <%Duration%> <%Location%> <%TaskInfo%> <%TaskType%> <%Task_Name%> <%Error_Code%> <%Error_Dscr%> <%Reason%>
To create a template configure the following options.
Name: Specify a descriptive name that is recognizable in a list of other templates.
Email Subject: Enter a descriptive subject so that recipients can easily identify the purpose of this message. Use a dynamic variable <%NotificationTypeAlertName%> to have the alert type added automatically. The following values depending on alert type are available:
- “Alert” in case the device is Down because of error.
- “All Clear” in case the device is no longer in the alerting state.
- “Test” in the case of Test Alert.
Email Reply-To: Specify the address that will be used if a recipient attempts to reply to this automated message.
Type: Select the format of the message − plain text (TXT) or HTML.
An alert could be triggered by the following types of events:
- An Error, which means the alert has been triggered by the automated system.
- A Test, which means that a user has manually triggered the alert to make sure that the proper recipients are receiving the alert in the proper format.
- An Uptime Alert, which is an automated message that can be configured to send to recipients once a device has left an error state.
A template can be configured to contain the message of the source event in the body.
Error Source: If necessary, customize the default message contents of an Error event.
Test Source: If necessary, customize the default message of a Test event.
Uptime Source: If necessary, customize the default message of an Uptime event.