The Logicmonitor pull connector sends information from Event Management to Logicmonitor. It sends responses received from a Push connector in a bi-directional environment to Logicmonitor.
Before you begin
Role required: evt_mgmt_admin
About this task
Starting from the Xanadu release, the OOTB (Out-Of-The-Box) rules provided with the connector, which you have not previously used (i.e., neither activated, deactivated, nor modified), will now have theApply additional
matching rulescheck box set to true. Previously, this check box was disabled. This change allows you to execute more event rules or automation using the same filter conditions for the connector.
Enter values in the required fields, which are indicated by a red asterisk.
Field
Description
Name
Descriptive name for the connector.
Connector definition
Search for and selectLogic Monitor.
Credential
SelectBasic Authfor basic authentication. Provide access_id and access_key from Logicmonitor's token based API authentication in the credentials as the basic authentication username and password.
Host IP
The Logicmonitor IP address.
When adding bi-directional functionality for a Push connector, the Connector Instance name must match the Source Instance field of the event generated by that source.
The source of events islogicmonitorso you should create an instance with the namelogicmonitor.
Note:
The Update queue business rule in the Alert table identifies each manual update of the alert and updates the connector queue accordingly. By default, changes to all alert fields are tracked.
Select the Active check box and select Save.
Note:
The LogicMonitor pull connector does not retrieve Events or populate the Events [em_event] table.