Alerts

Alert delivery methods

LogicMonitor supports several methods of delivering alerts:

 

Text Message (SMS) Alert Delivery

LogicMonitor supports two methods of delivering alerts via text messages: via an email-to-sms gateway ('SMS Email'), and by native SMS.

Text Message (SMS) Alert Delivery

SMS Email

An email to sms gateway is simply an email address that can be used to deliver sms or mms messages.  The advantages of this method are that it is generally free of carrier charges, and because most email to sms gateways and phones preserve the subject line or body in replies, it is easier to respond to alerts simply by replying to the message.  The disadvantage is that it depends on the availability of your phone provider making this email gateway available - something commonly done in the United States, but not in all other countries.

SMS email alert notifications are formatted based on the default email alert message templates in your account, unless a custom message template is defined for the datapoint, eventsource, batchjob, service, etc. in alert. The format for SMS email alert notifications can be set to full (which will display the entire alert message) or short (limits the message to 160 characters).

To route alert notifications via SMS email, first ensure that an SMS email address is defined for a user in your account, then add a recipient in an escalation chain and set the contact method to the user's SMS email address.

For instructions on how to respond to SMS email alert notifications, see this help page.

Native SMS

Native SMS messages can be sent directly to a user's phone when the user's phone number is defined in their account. The advantage of native SMS is that it can be more reliable, and will work even where the provider does not provide an email-to-sms gateway address.  The disadvantages of this method are that it is harder to respond to alerts, as native SMS messages do not carry any context (the subject line of the original message is not sent back with the reply) so requires the user to enter the alert ID when responding to alerts.

SMS alert notifications are formatted based on the default SMS alert message templates in your account, unless a custom message template is defined for the datapoint, eventsource, batchjob, service, etc. in alert.

To route alert notifications via native SMS, first ensure that a phone number is defined for a user in your account, then add a recipient in an escalation chain and set the contact method to the user's SMS phone number.

For instructions on how to respond to native SMS alert notifications, see this help page.

 

Email Alert Delivery

LogicMonitor allows you to route alert notifications to an email address a couple of different ways:

  1. Normal email alert delivery
  2. Custom email alert delivery

Normal Email Alert Delivery

Normal email alert delivery will send alert notifications according to the alert message defined in the definition of the datapoint in alert, or according to the default alert message template if no custom message is defined for the datapoint. This has the advantage that the email can be formatted specifically for the alert, and can include explanatory information or advice on how to react to the alert. For example, consider the following email alert:

The host prod5 is experiencing an unusual number of failed TCP connections, probably incoming connections. There are now 4.16 per second failed connections, putting 
the host in a warn level.

This could be caused by incorrect application backlog parameters, or by incorrect OS TCP listen queue settings.

Email alert notifications are formatted based on the default email alert message templates in your account, unless a custom message template is defined for the datapoint, eventsource, batchjob, service, etc. in alert.

To route alert notifications via email, either:

  • add a user as a recipient in an escalation chain and set the contact method to email; OR
  • add an arbitrary email address to the CC field in the recipient field for an escalation chain

For instructions on how to respond to email alert notifications, see this help page.

Custom Email Alert Delivery

Custom email alert delivery allows you to format alert notification emails in a more consistent format, without explanatory text. This can be advantageous if you're sending alert notifications to a ticketing system, for example. Custom email alert delivery enables you to define the precise format of the email subject and body using tokens, so that it can be easily parsed by the recipient system. For example consider the following custom email alert:

Host: ip-172-31-33-214.us-west-2.compute.internal
                   Datasource: Ping
                   Datapoint: average
                   Level: warn
                   Start: 2015-10-09 14:44:13 PDT
                   Duration: 0h 0m
                   Value: No data
                   Reason: average

Custom email alert notifications are formatted based on the subject and email body in the definition of the custom email alert delivery method.

To route alert notifications via custom email delivery:

  1. define a custom email alert delivery method; and
  2. add a user as a recipient in an escalation chain and set the contact method to the custom email alert delivery method you defined in step 1.

For instructions on how to respond to email alert notifications, see this help page.

 

Voice Call Alert Delivery

You can choose to have LogicMonitor alert notifications delivered to users in your account via voice calls. These notifications will be formatted based on the default email alert message templates in your account, unless a custom message template is defined for the datapoint, eventsource, batchjob, service, etc. in alert.

To route alert notifications via voice calls, add a user as a recipient in an escalation chain and set the contact method to voice for that user. Note that voice alerts do support international calls - simply format the international phone numbers using E.164 number formatting. E.164 numbers can have a maximum of fifteen digits and are usually written as follows: [+][country code][subscriber number including area code].

  • For example, to convert a US phone number (415 599 2671) to E.164 format, one would need to add the '+' prefix and the country code (which is 1) in front of the number (+1 415 599 2671). In the UK and many other countries internationally, local dialing requires the addition of a 0 in front of the subscriber number. However, to use E.164 formatting, this 0 must be removed. A number such as 020 7183 8750 in the UK would be formatted as +44 20 7183 8750.


You can acknowledge, SDT, or escalate alerts delivered via voice notifications by responding on your phone's keypad (the notification message will provide instructions for doing so).

 

Custom HTTP Alert Delivery

Custom HTTP Alert Delivery Methods (i.e. Webhooks) allow you to send alert notifications to an external system via HTTP GET or POST requests. Similar to Custom Email Alert Delivery, this can be advantageous if you're sending alert notifications to a ticketing system. Custom HTTP alert delivery enables you to define the precise format of the alert notification using tokens (variables), so that it can be easily parsed by the recipient system. For example consider the following alert notification posted to a HipChat room:

Custom HTTP alert notifications are formatted based on the subject and email body in the definition of the custom HTTP alert delivery method.

To route alert notifications via custom email delivery:

  1. define a custom HTTP alert delivery method; and
  2. add a user as a recipient in an escalation chain and set the contact method to the custom HTTP alert delivery method you defined in step 1.