- About LogicMonitor
- About Alerts
- Alert Delivery
- AIOps Features for Alerting
- Responding to Alerts
- Alert Integrations
- Alert Integrations Overview
- ServiceNow (Incident Management) Integration
- Slack Integration
- Puppet 4 Integration
- Slack Integration: LogicMonitor App Beta
- ConnectWise Integration
- Autotask Integration
- Custom HTTP Delivery
- Custom Email Delivery
- Puppet Integration
- PagerDuty Integration
- Campfire Integration
- Zendesk Integration
- Integrations Logs
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
LogicMonitor can raise alerts for:
There is an overall Alerts page available from the left-hand main menu that displays all alerts across your entire LogicMonitor account, as well as filtered Alerts pages (i.e. tabs) that are available from the detail pages of your various devices, cloud resources, instances, websites, services, and groups.
DataSources define the numerical data, called datapoints, that will be collected through periodic polling from a Collector. An alert on a DataSource is the most common type of alert and is triggered when datapoint values that a Collector receives from a device exceed the threshold(s) you’ve specified—or when there is an absence of expected data.
For more information on configuring alerts on DataSource datapoints, see Datapoint Overview.
EventSources watch particular files such as event log messages (IPMI, Windows, or Syslog) or SNMP traps. An alert on an EventSource is triggered when LogicMonitor receives a message for an event that matches an EventSource definition.
For more information on configuring alerts on EventSources, see Creating EventSources.
Websites can be monitored to ensure their availability. An alert on a website is triggered when a specified number of checks fail at a specified number of test locations.
For more information on configuring alerts on websites, see Website Alerts.
JobMonitors on Windows and Linux/Unix systems can be monitored to ensure that jobs start on time, complete when expected, and exit with the proper exit code. An alert on a JobMonitor is triggered when a monitored job exits with a non-zero exit code, doesn’t complete within a specified run time, or doesn’t start on time.
For more information on configuring alerts on JobMonitors, see Creating JobMonitor Definitions in LogicMonitor.
Device groups are collections of strategically grouped devices. Alerts for device groups, called Cluster Alerts, are triggered based on the overall state of the group. For example, you could configure a Cluster Alert to trigger when more than five batch servers within a device group have CPU usage rates over 80%.
For more information on configuring Cluster Alerts, see Cluster Alerts.
Collectors are LogicMonitor applications that run on servers within your infrastructure in order to intelligently monitor devices within your infrastructure. An alert on a collector, called a Collector Down Alert, is triggered when LogicMonitor has not heard from a Collector for more than five minutes.
Services are instances across one or more monitored resources (e.g. devices) that have been grouped into a logical “service”. Data can then be aggregated across these instances for monitoring, visualization, and alerting on this data at the service level. For more information on Services, see About LM Service Insight.
ConfigSources generate alerts based on config checks. Much like a datapoint and threshold in a DataSource, a config check monitors the availability of a config file, or specific contents of the file, and triggers an alert when defined criteria are met. For more information on ConfigSources, see Creating ConfigSources.
In this Article: