Customizing Email Alerts and Notifications

  1. Select the check box for the service in the Services view.
  2. In the Alerts list, select Alert and Notification Settings. The Alerts window appears.
  3. Click to the right of the notification type you wish to customize. The window expands.
  4. Select the severity of the error/violation from the list. There are three severity levels: Alert, Warning, and Ignore.
  5. In the Contact list, select either Alert Message or Diagnostic Message. See Configure_alerting_options for information on adding contacts.
  6. Modify the text in the Subject field, if desired.
  7. Modify the Message text, if desired. See variables for dynamic text.
  8. Click Save to save your changes and create your message template or click Apply Templates Across All Services.

Apply Templates Across All Services

  1. Click Apply Templates Across All Services. The Replicate Messages Across Services window appears.
    Note: You can only replicate messages to services of the same type. For example, a DNS type service may only share templates with other DNS services.
  2. Select the check boxes of the services to which you want to replicate the message template and click OK (click to view larger image).

Message Variables

You can use the following variables to further customize your email alerts and notifications.

{TYPE}: The type of error message.
{MESSAGE}: The error message text.
{URL}: The URL where the error occurred.
{LOG_LINE}: A line which returns {TYPE} {MESSAGE} {URL}
{CONTENT}: The content retrieved from the referenced URL
(CONTENT, TIMEOUT, etc) and the URL of the actual error.
{LOG_LINK}: A link to the logs in the user's account.
{PATH}: an alias to {URL}.
{TIME}: Time the error was reported.
{TIMEZONE}: Timezone of where the server is located.
{SEVERITY}: The type of the notification: Alert or Warn.
{TRACERT}: A trace route from the agent to the URL being referenced.
{STEPDESCRIPTION}: For Application Monitors only. If your script fails at a particular step (for example Add to Cart), the failing step will be sent.
{AGENT}: The location of the agent which performed the test.
{AGENT_IP}: The IP of the testing agent.
{SERVICE}: The name of the monitoring service which threw the error.
{DESCRIPTION}: A description of the service.
{SERVICE_TYPE}: The type of service.
{START}: The first reported instance of the error. If no error have been reported before, return the current time
{STOP}: The current time.
{ELAPSED}: Elapsed time from the first error on this service to the current time.


For all strikes, you can use {ADDITIONALERRORS} to loop over the different errors. For example, you can display the first Agent and first Agent ID using
Agent(s): {AGENT} ({AGENT_IP})
For additional errors and agents, you can put {ADDITIONALERRORS}, {AGENT} ({AGENT_IP}){/ADDITIONALERRORS} and list the additional agents and IPs in this particular strike list

Notifications available for all service types


The client did not complete the request in the configured timout value.


The server could not reach the site.


Specified content not found on a page.

Notifications available for specific service types


Verifies a DNS service's URL matches its IP address.


Indicates that the service is not meeting the SLA (Service Level Agreement) configured in Settings > SLA / Objectives or the service's Alert and Notification Settings dialog.


Verifies the quality of multimedia (for example, Flash videos).

See also