Creating an Alert
This template option is the basic alert template and contains only the most common, simple
The simple email screen looks like this:
Features of the Email (simple) template include:
An Example of a simple Email alert is:
Where this alert:
The standard output of the email is:
Email with custom content (simple)
The purpose of this template is to keep the filter and advanced email components as simple as
In many cases is desirable to have a tailored email subject line or different content in the
The Email section in this template has been expanded into its own section:
Using the same example as above with the Adelaide Router the output of the standard email
Hint: Use the Preview Test Email to see the output of your alert.
In this example the user now wants to change the alert as follows:
The Alert Configuration Screen now looks like this:
Using the Preview Test Email option the output has now changed to show the new
Email with custom content (advanced)
The purpose of this template is to provide access to all of the Emailer options. This template
After clicking the (+) different filters can be created using multiple event types. eg: Device,
Send syslog message
The purpose of this template is to allow customers to send syslog messages.
Run a custom script
This template is for advanced users:
Create a new alert
Edit an alert
Delete an alert
Examples of Alerts
The following alerts have been outlined to provide examples of the functionality available
Example 1: Simple Device Down Email Alert
Example 2: Simple Interface OperStatus state change with bundling
A test email has been created to see what the output will look like:
Example 3: Simple email alert with custom Content
Example 4: A Bundled Interface State change Email Alert on a Core Router Interface with custom subject and comments.
Example 5: A Broadcast Storm Alert using an alert of syslog with multiple filter criteria and customised content
Example 6: Morning Email Alert for WAN Interfaces that had an OperStatus change overnight.
Example 7: Sending a Syslog Alert to another host for a Network Device CPU utilization exceed event.
Example 8: Sending a Syslog Alert to another host for a Network Device CPU utilization exceed event.
Custom actions can be written by customers to perform many actions not supported by