- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- Implementation Readiness
- I just signed up for LogicMonitor, now what?
- Advanced LogicMonitor Setup
- LogicMonitor Security Best Practices
- Defining Authentication Credentials
- Adding devices when they boot
- Network scanning for additional devices
- Credentials for Accessing Remote Windows Computers
- Why am I receiving account lock out alerts?
- Running without Administrator Privileges in Windows
- How do I get support resources?
- LM Service Insight
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
LogicMonitor allows you to route alert notifications to different teams within your organization, so that the right people are notified when an issue occurs. Alert notifications can be delivered via email, text message, or even a voice call. Alert notifications can also be delivered to third-party team collaboration systems (e.g. ServiceNow, PagerDuty, etc.). If a recipient is unable to deal with or respond to the alert, the alert is automatically sent to the next person in the escalation chain—this process repeats until the alert is acknowledged or cleared.
There are two primary components that make up LogicMonitor’s alert routing:
- Alert rules. When an alert is triggered, an alert rule specifies the escalation chain to which the alert should be routed. For more information, see Alert Rules.
- Escalation chains. Escalation chains specify the people (or third-party applications) to which alert notifications should be sent. For more information, see Escalation Chains.
By default, your LogicMonitor account comes with alert rules that are configured to match all alerts. These rules point to escalation chains with no recipients. This means that alerts matching these rules are not routed and will only appear in the LogicMonitor interface. If you would like these default alert rules to deliver to recipient(s), you can further configure recipients for the escalation chains.
If you keep these default rules in place, change the values of their Priority fields to larger values. As discussed in Alert Rules, this will help ensure that they are only triggered if no other custom (or more specific) rules trigger for the same alert.
After you’ve configured your datapoint thresholds and alert routing, you can move on to setting up dashboards to view your monitored data.
In this Article: