Alert Delivery Methods

Email alerts are sent from [email protected]. The default subject line of email alerts looks like this:

When the error is resolved, the notification subject line looks like this (ST=0 means “no error”):

Alert contents can be formatted as HTML or plain text. You can customize alert contents by using alert templates.

This method sends a text message to a cell phone via that phone’s email address that was provided by the cell phone company. Many cellular carriers in the US, UK and Canada support this method. There are no additional charges from AlertSite for using this method.

Here are examples of cell phone email addresses for different cellular carriers:

Email-to-text alerts have the following format by default:

For example, an alert for an error found from the Fort Lauderdale location might look like this:

You can change the alert format by creating custom alert templates.

AlertSite can send SMS (text messages) to cell phones, PDAs and similar wireless devices. Your mobile provider must support SMS.

Prerequisites

Usage

You can receive alerts as phone calls to a number of your choice. If answered, the call announces alert condition, otherwise a voice message is left. There are no additional charges from AlertSite for using this method, but there may be charges from your telephone service provider.

When configuring a VoIP recipient, enter your phone number in this format:

AlertSite VoIP alerts come from the US number 954-800-2545.

You can integrate AlertSite with PagerDuty to trigger incidents in PagerDuty when an AlertSite monitor detects an error. For details, see PagerDuty Integration.

Use the ServiceNow integration to automatically create incidents in ServiceNow based on alerts from AlertSite. See ServiceNow Integration.

AlertSite can send availability and performance alerts to your Splunk server. For details, see Splunk Integration.

Alerts can be sent to alphanumeric pagers via a special protocol. If you want to use this notification method, please contact SmartBear support.

Alphanumeric pager alerts have this format:

Alerts can be sent to numeric pagers. AlertSite supports two methods of alert delivery:

• Pause after dial – Dials a pager number and waits 10 seconds before delivering the numeric message.

• Wait for quiet – Waits for a “quiet” period after dialing before sending the numeric message (more reliable than “pause after dial”).

When creating a numeric pager recipient, enter the pager’s phone number in this format:

Alert Format

Alerts sent to numeric pagers are a combination of status code, monitor type code, and the last three digits of the IP address of the target site.

The format of numeric pager messages is 777, followed by:

• Two digit AlertSite status code (00-99)

• Two digit monitor type code:

  • 01 – web URL or API monitor monitor
  • 02 – web URL or API monitor monitor for https://
  • 03 – Email (POP) monitor
  • 04 – Email (SMTP) monitor
  • 05 – DNS monitor
  • 06 – FTP monitor
  • 07 – TCP monitor
  • 08 – Email (IMAP) monitor
  • 09 – Round-trip email monitor
  • 10 – ServerAgent
  • 11 – security scan
  • 12 – real-browser (DéjàClick) monitor
  • 14 – SoapUI monitor
  • 16 – Selenium monitor

• The last three digits (octet) of the IP address being monitored (000-999)

For example, if the alert is triggered for a site with an IP address 216.65.123.194 due to a TCP connection failure (AlertSite status code 01), the numeric pager would receive 7770101194:

When the problem has resolved, the pager would receive 7770001194 (status 00 = no error).

Alerts can be sent via an HTTP POST request with JSON payload. JSON payload can be customized as per your requirements. This method can be used to integrate AlertSite with JSON Alerts for details.

Alerts can be send via HTTP POST request with data in the application/x-www-form-urlencoded format. The request body contains the monitor and error information as field=value pairs:

Below are the decoded values with line breaks added for readability. For a description of these values, see Alert Data Fields.

This method sends an SNMP trap to a specific IP address with a trap listener. For details, see SNMP Alerts.