Alert notifications are typically sent directly from servers within LogicMonitor's data centers. With External Alerting, one of your Collectors pulls triggered alerts from LogicMonitor and delivers them as SNMP traps, Syslog messages, or by using custom script.
You can define one or multiple External Alerting entries to process alerts, however you can only have one External Alerting entry per Collector.
Adding & Editing External Alerting
You can add a new External Alerting entry or edit an existing External Alerting entry from Settings | Alert Settings | External Alerting
The device group(s) for which your Collector will process external alerts. Glob expressions are supported.
The Collector that will process alerts for the specified groups.
You can only have one External Alert entry per Collector. You can create a new Collector specifically for this task.
For example, if all existing Collectors are in data centers collecting data, but cannot reach an internal ticket management system due to firewall rules, you could install a new Collector dedicated to External Alerting.
How the Collector will deliver alert messages for the specified groups. Select from SNMP trap, Syslog, and script.
With SNMP trap delivery your collector will send an SNMP trap to an SNMP trap server for each alert triggered on the group(s) specified. Note that SNMP traps must be less than 1024 bytes, so the message may be truncated
SNMP Trap Server
The server to which SNMP traps should be sent. SNMP traps will be sent with the LogicMonitor enterprise OID: 18.104.22.168.4.1.39832
The community string required for the Collector to send an SNMP trap to the specified server.
The version of SNMP that the Collector should use to send SNMP traps.
With Syslog delivery the Collector will send a Syslog message to a Syslog server for each alert triggered on the group(s) specified.
The server to which Syslog messages should be sent.
With Script delivery the collector will execute a script for each alert triggered on the group(s) specified.
The script executed by the Collector for alert delivery.
Script Command Line
Any arguments or parameters to be passed to the script. Any of the DataSource, EventSource, or JobMonitor tokens can be used as parameters to be passed to the script.
We recommend that the script use tokens common to ALL alert types. If not, it should be constructed to function in the presence or absence of specific arguments, which vary based on the alert type.