- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- LM Logs
- LM Service Insight
- About LogicModules
- Creating & Managing DataSources
- Active Discovery
- Data Collection Methods
- Groovy Support
- PowerShell Support
- Setting Up JobMonitors
- Help & Troubleshooting
- User-Defined AppliesTo Functions
- SNMP sysOID Maps
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
LogicModules are templates that define how LogicMonitor should access, collect, alert on, and configure data coming from your monitored infrastructure. LogicModule definitions can be viewed, edited, and created from the Settings page (Settings | LogicModules). As discussed next, there are eight types of LogicModules.
DataSources define what numeric time-series data should be collected, how it should be collected, and what values should be graphed and trigger alerts. LogicMonitor comes with over a thousand pre-configured DataSources to allow you to instantly begin monitoring the majority of devices in your infrastructure, with new DataSources continually being added.
For more information, see our set of DataSource support articles.
EventSources define monitoring and alerting activity for non-numeric event-based data. There are two types of EventSources:
- EventSources that monitor asynchronous event messages received by the Collector
- EventSources that actively monitor event logs or log files for the presence of specific events
EventSources monitor for the following types of events:
- IPMI event log events
- SNMP traps
- Windows event logs
- Syslog events
For more information on EventSources, see our set of EventSource support articles on the topic.
ConfigSources use embedded Groovy or PowerShell scripts to access, collect, and alert on changes to your devices’ configuration files. For more information, see our set of ConfigSource support articles.
PropertySources provide a means of programmatically configuring device properties using an embedded Groovy or PowerShell script. Arbitrary properties and values can be assigned to devices using PropertySources. Automated property assignments can be used for such purposes as inventory tracking and reporting, troubleshooting, and dynamic grouping.
For more information, see Creating Property Sources.
TopologySources enable LogicMonitor’s topology mapping capabilities. Pre-built by LogicMonitor, TopologySources leverage layer 2 discovery protocols (i.e. LLDP and CDP) to gather information that is used to define logical relationships among the many monitored devices in your network.
For more information on how TopologySources facilitate topology mapping, see Topology Mapping Overview.
JobMonitors monitor batch jobs on Windows and Linux/Unix systems to ensure jobs start on time, complete when expected, and exit with the proper exit code. Job monitoring is enabled using a supplied wrapper script to run the batch job. The wrapper script sends information to the Collector about the job execution.
For more information, see our set of JobMonitor support articles.
AppliesTo Functions are used to apply LogicModules to devices, specify criteria for membership in dynamic groups, configure dashboard widgets, and perform other various functions across the LogicMonitor platform.
For more information, see AppliesTo Functions.
SNMP SysOID Maps
SNMP SysOID Maps are used to classify devices that respond to SNMP. A SysOID Map consists of two parts: a full or partial sysOID, formatted as a regular expression, and one or more categories associated with that sysOID. When a device responding to SNMP is added for monitoring, its SysOID is checked against the entries in the SNMP SysOID Maps. When a match is found, the corresponding categories are added to the system.categories property of the device.
For more information, see SNMP SysOID Maps.
In this Article: