Alerts

Responding to email/SMS email alert notifications

When you receive alert notifications via email/SMS email, you can click the link in the alert email or SMS message to respond to your alerts in your browser. But you can also reply to the alert directly via SMS or email.

Note: Replies to SMS alert messages received through an email to sms gateway (as opposed to native SMS) will only be delivered if the subject line is maintained. This is a restriction of the carrier - if the subject line is removed by the phone when replying, the reply will not be delivered to LogicMonitor. This is a known issue with some Android phones. In this case, you can reply to the alert via using the email app, or have the alert delivered by native SMS.

 

Email/SMS email response commands

Use the following commands in the body of the reply to an email or SMS email alert notification:

Response Command

Description

ACK [optional comment] Acknowledge the alert, with a comment if one is specified. The alert will be acknowledged, stopping any escalations. As usual, the ACK and comment will be sent to the cc list for that Alert Chain, if any.
NEXT Immediately escalate to the next stage in the escalation chain, without waiting for the escalation interval to pass. You can use this command if you get an alert, but are not in a situation to respond.
SDT [alert ID] [SDT duration in hours] [optional comment] Schedule downtime (SDT) for the instance in alert, for X hours. The value can be a decimal fraction to schedule SDT for less than an hour: e.g. SDT .25 = 15 minute SDT. For example, if you receive an alert for disk D: space usage on device Beta, a reply of 'SDT 1' will schedule downtime for 1 hour, for only that specific disk. Alerts on other disks will still be routed. The comment, if included, will be sent to others to whom the alert has already been escalated.
SDT [DataSource X][SDT duration in hours] [optional comment] Schedule downtime (SDT) for the specific datasource that triggered the alert, for X hours. The value X can be a decimal fraction to schedule SDT for less than an hour: e.g. SDT datasource .25 = 15 minute SDT. For example, if you receive an alert for disk D: space usage on device Beta, a reply of 'SDT datasource 1' will schedule downtime for the entire disks datasource on Beta. This means that alerts will not be routed for all disks on Beta (SDT disables routing, but you can still see alerts triggered during SDT in your account). Other alerts (e.g. CPU) triggered on Beta will still be routed.
SDT [host X] [SDT duration in hours] [optional comment] Schedule downtime for the specific device for X hours. The value X can be a decimal fraction to schedule SDT for less than an hour: e.g. SDT host .25 = 15 minute SDT. This will disable routing for all alerts triggered for the device until the SDT has expired.

Example

Let's take a look at an SMS response using option 3 (SDT [alert ID] [SDT duration in hours] [comment]).

Supposed you receive the following message via SMS: 

LMD121155 error
Instance100 CPU
Duration: 0h 5m
CPUBusyPercent = 85.1043

If I wanted to respond to this message by SDTing the instance for 2 hours while I troubleshoot, I would write the following: 

 SDT  LMD121155  2 

I simply used the format listed in the above table to SDT the instance for 2 hours. Please note that you have to include the full alert ID received in the initial SMS message in order to properly respond to an alert.