{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30320,"path":"it-operations-management/event-management/configure-logic-monitor-connector.md","title":"Configure event collection from Logicmonitor","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure event collection from Logicmonitor\n\nThe 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.\n\n## Before you begin\n\nRole required: evt\\_mgmt\\_admin\n\n## About this task\n\nStarting 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 the**Apply additional matching rules**check 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.\n\n**Note:** This feature applies only to active event rules.\n\n## Procedure\n\n1.  Navigate to**All** > **Event Management** > **Event Connectors \\(Pull\\)** > **Connector Instances**.\n\n2.  Click**New**.\n\n    The**Connector Instance New Record**page appears.\n\n3.  Enter values in the required fields, which are indicated by a red asterisk.\n\n    |Field|Description|\n    |-----|-----------|\n    |**Name**|Descriptive name for the connector.|\n    |**Connector definition**|Search for and select**Logic Monitor**.|\n    |**Credential**|Select**Basic Auth**for 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.|\n    |**Host IP**|The Logicmonitor IP address.|\n\n    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.\n\n    \\[Omitted image \"logicmonitor-list.png\"\\] Alt text: Connector Instance name matching Source Instance name\n\n    The source of events is**logicmonitor**so you should create an instance with the name`logicmonitor`.\\[Omitted image \"logicmonitor-list-results.png\"\\] Alt text: Name is logicmonitor\n\n    **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.\n\n4.  Select the **Bi-directional** and **Active** check boxes, and then click **Save**.\n\n    The LogicMonitor pull connector does not retrieve events or populate the Events \\[em\\_event\\] table.\n\n\n**Parent Topic:**[Configure a pull connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/t_EMConfigureConnectorInstance.md)\n\n"}}