Using AlertSite UXM > Alerts > Alerting Methods

Alerting Methods

AlertSite UXM can sent alerts to various notification channels. To learn how to add recipients for alerts, see Creating Alert Recipients.

Notification Method AlertSite UXM Plans Alert Types
Free Pro Enterprise Availability Performance
E-mail (HTML or text) + + + + +
Telephone message (VoIP) *     + * +  
Telephone message     + +  
SMS     + +  
Email to wireless device (cell phone, pager, Blackberry, and so on)     + + +
PagerDuty     + + +
Splunk     + + +
Pager:     + +  
POST request to a web server     + +  
SNMP trap     + +  
AOL Instant Message (AIM)     + +  

* VoIP alerts are not available during trial.

E-mail (HTML or text)

Email alerts are sent from alerts@alertsite.com. If remote commands are enabled in the recipient properties, alerts are sent from alerts+monitorID@pages.alertsite.com, where monitorID is the ID of the monitor that triggered the alert.

The default subject line of email alerts looks like this:

[AlertSite] Site/Device Alert (ST=status code) - Monitor_name Error_description

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

[AlertSite] Site/Device Alert (ST=0) - Monitor_name

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

E-mail to wireless device (cell phone, pager, Blackberry, and so on)

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:

AT&T AreaCodePhoneNumber@txt.att.net
Sprint AreaCodePhoneNumber@messaging.sprintpcs.com
T-Mobile AreaCodePhoneNumber@tmomail.net
U.S. Cellular AreaCodePhoneNumber@email.uscc.net
Verizon AreaCodePhoneNumber@vtext.com
Examples of paging carriers:
Skytel Accessnumber@skytel.com

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

Site Name (Monitor type) [Status code, Description, Timestamp, Location]

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

My Monitor Name (Web Site) [1, Error-TCP Connection Failed, 04-15 15:30, Fort Lauderdale]

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

SMS

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

Note: There are additional charges for sending SMS alerts. Please contact your AlertSite Sales Representative for details.

When creating an SMS recipient, specify the phone number in the following format:

Region Format Example
United States and Canada 1 area-code number 12125551212
International country-code number (without leading +) 493206922000

SMS alerts have this format:

AlertSite:

Monitor name, status code, Error description

Location

Timestamp

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

AlertSite:

My Monitor Name, 9, Ping Failed

Fort Lauderdale

15:30 04/15/14

Telephone message (VoIP)

You can receive alerts via 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:

Region Format Example
United States and Canada 1 area-code number 12125551212
International 011 country-code number (without leading +) 011493206922000

AlertSite VoIP calls come from these US numbers:

However, our VoIP provider may change without notice.

PagerDuty

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

Splunk

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

Alphanumeric (text) pager

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:

AlertSite:

Monitor name, status code, Error description

Location

Timestamp

Numeric pager

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

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

Region Format Example
United States and Canada 1 area-code number 12125551212
International 011 country-code number (without leading +) 011493206922000

Note: We do not recommend using numeric pagers for alerts. They provide little or no error-detection or recovery capability, and are best left for human-only use.

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 message is prefixed with 777 to identify it to the recipient as an AlertSite message.

777 – standard prefix
Two digit AlertSite status code (00-99)
Monitor type code:
  01 – web URL monitor
  02 – secure URL monitor
  10 – ServerAgent
  12 – real-browser (DéjàClick) monitor
  14 – SoapUI API monitor
  15 – Perfecto Mobile monitor
  16 – Selenium monitor
The last three digits (octet) of the IP address being monitored (000-999)

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:

Format of numeric pager alerts

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

POST request to web server

AlertSite can send alert data to your web server using an HTTP POST request. The request body contains the monitor and error information as field=value pairs:

POST /your/url HTTP 1.1
Host: yourserver.com
Content-Type: application/x-www-form-urlencoded
User-Agent: ipd/1.0 (ipd; IPD 1.0; AlertSite)
Content-Length: 353

 

source=AlertSite&custid=C12345&company=AlertSite%20Demo&device_id=121352&device_name=Home%20Page&timestamp=2015-09-17%2012:50:03&status=7&errcount=1&status_text=HTTP%20error%20from%20web%20server&location=Fort%20Lauderdale,%20FL&location_num=10&device_typecode=w&device_type=Web%20Server&transaction=0&http_status=HTTP/1.1%20503%20Service%20Unavailable&

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

source=AlertSite

custid=C12345

company=AlertSite Demo

device_id=121352

device_name=Home Page

timestamp=2015-09-17 12:50:03

status=7

errcount=1

status_text=HTTP error from web server

location=Fort Lauderdale, FL

location_num=10

device_typecode=w

device_type=Web Server

transaction=0

http_status=HTTP/1.1 503 Service Unavailable

SNMP trap

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

Note: Because SNMP traps use UDP, they are unreliable across public networks. A more reliable solution is to send alerts via a POST request to your own web server, and then send the trap through your local network. For an example, see Creating an SNMP Trap.

AIM (AOL Instant Message)

You can receive alerts via AIM (AOL Instant Message) to instant messaging clients such as AOL Instant Messenger, Pidgin, Trillian, and others. We recommend AIM version 6 or later for proper message formatting.

Note: Alert delivery via AIM is not guaranteed. We recommend that you use additional notification methods together with an AIM.

To configure AIM alerts:

  1. In your AIM client, add the Screen Name AlertSite to your buddy list.
  2. In AlertSite, add an AIM recipient and specify your AIM Screen Name.

You can use customize the contents of AIM alerts by using alert templates.

See Also

© 2017 SmartBear Software. All rights reserved.      Terms of Use · Privacy Policy