Overview You can use the Script EventSource collection method to detect and alert on any event.  This may be useful if you have custom logging that can’t be monitored with the other EventSource collection methods (log files, windows event logs, SysLogs, and SNMP traps). To create an EventSource using this collection method, set the EventSource … Continued

Using the Syslog EventSource, LogicMonitor can monitor syslog messages pushed to the Collector for alerting purposes only. The Syslog EventSource is not intended as a syslog viewing or searching tool.  For Syslog viewing and searching, you can use LM Logs. See Collecting and Forwarding Syslog Logs. Setting Up Syslog Monitoring To set up your system … Continued

Overview SNMP traps involve the monitored device sending a message to a monitoring station (the LogicMonitor Collector in our case) to notify of an event that needs attention. Through the creation of an EventSource, LogicMonitor can alert on SNMP traps received by the Collector. Preferred Alternatives to SNMP Trap Monitoring LogicMonitor generally recommends SNMP polling … Continued

Overview LogicMonitor can detect and alert on events recorded in most Windows Event logs.  An EventSource must be defined to match the characteristics of an event in order to trigger an alert. When a collector detects an event that matches an EventSource, the event will trigger an alert and escalate according to the alert rules defined. Note: LogicMonitor does not … Continued

Overview LogicMonitor lets you monitor log files generated by your OS or applications such as MySQL, Tomcat, and so on. For example, you can monitor the MySQL slow query log so an alert will be triggered every time a slow query is logged in the log file. Note: A LogicMonitor Collector must have direct file … Continued