---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Event collection from Logicmonitor

# Event collection from
Logicmonitor {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

The MID WebService Event Collector enables you to collect JSON formatted event
messages from the Logicmonitor.

## Before you begin

Ensure that the Event Management Connectors (sn_em_connector) plugin is
installed on the ServiceNow AI Platform instance.  
Ensure that you:

* Deploy and start the MID Server. See [MID Server
  configuration](https://www.servicenow.com/docs/access?context=c_MIDServerConfiguration&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) .
* Configure and start the MID Web Server. See [Configure the MID Web Server extension](https://servicenow-prod.fluidtopics.net/_6TI0U~gdVg0W_7HIWP7AA "The MID Web Server is a MID Server extension that enables developing REST APIs to send events and metrics to the MID Server. The extension is leveraged by other MID Server extensions, such as Metric Intelligence, MID WebService Event Listener, and the Agent Client Collector websocket endpoint extension.").
* Configure and start the MID WebService Event Collector. See [Configure the MID WebService Event Collector Context](https://servicenow-prod.fluidtopics.net/9hyUIqDCjbtMOV2bYDXigQ "Configure the MID WebService Event Collector Context to provide a URL method to push event messages from an external source to the MID Server.").
{#event-collection-logicmonitor__ul_d21_gkf_cy}

Role required: evt_mgmt_admin

## About this task

JSON formatted event messages are sent from Logicmonitor. The MID Server transforms the collected event messages by parsing them using the
TransformEvents_MidLogicmonitor script include, located here: Event ManagementIntegrationsPushConnectors. In the Push Connectors page, click Logicmonitor Mid Push Connector.

The default format of the URL to push event messages from Logicmonitor to the MID Server is
<kbd class="ph userinput">http://&lt;MID_Server_IP&gt;:&lt;MID_Web_Server_Port&gt;/api/mid/em/inbound_event?Transform=TransformEvents_MidLogicmonitor</kbd>.  
{#event-collection-logicmonitor__table_bbq_cmk_k2b__entry__2}

| Variable | Description |
|-|-|
| MID_Server_IP | IP address of the MID Web Server Extension. |
| MID_Web_Server_Port | Listening port of the MID Web Server Extension. |
| MID_Web_Server_User | Username for the MID Web Server Extension. |
| MID_Web_Server_Password | Password of the user of the MID Web Server. |
[Table 1. Variables in the default URL]

{#event-collection-logicmonitor__table_bbq_cmk_k2b}

## Procedure

1. In the Logicmonitor console, create a custom HTTP Delivery integration.
   1. Navigate to SettingsIntegrations and click AddCustom HTTP Delivery Integration.
   2. In the Manage Custom HTTP Delivery Integration form, fill in the Name and Description field and select the Use the same URL and data to notify on various alert activity check box.
   3. Specify when to send a notification on alert activities by selecting the Acknowledged, Cleared, and Escalated/De-escalated check boxes as needed.
   4. In the HTTP method menu, select HTTP POST.
   5. Fill in the Username and Password field, and enter a URL with the format as, <kbd class="ph userinput">http://&lt;MID_Server_IP&gt;:&lt;MID_Web_Server_Port&gt;/api/mid/em/inbound_event?Transform=TransformEvents_MidLogicmonitor</kbd>.
   6. Under the Alert Data section, select Raw and select the format as JSON.
   7. Add the custom payload provided in the description of the connector.
   8. Click Test Alert Delivery to verify the connection or Save.
   {#event-collection-logicmonitor__substeps_dz1_2zh_kqb}
2. When you're finished creating the integration, create an escalation chain for the alert settings.
   1. Navigate to SettingsAlert SettingsEscalation Chains and click Add.
   2. In the Manage Testing chain form, fill in the Name and Description field and select the rate at which the alerts should be notified.
   3. Under the Stages section, select the Add icon ![logicmonitor add icon]() to add a stage and click Save.
   4. When you create the new stage, select the Add icon ![logicmonitor add icon]() again to search for the user and add the integration as the Contact Method and click Save.
   {#event-collection-logicmonitor__substeps_ibp_nzy_lqb}
3. After creating the escalation chain, configure alert rules for the chain you created.
   1. Navigate to SettingsAlert SettingsAlert Rules, and click Add.
   2. On the Add Alert window, configure the conditions that initiates the alerts when conditions are violated.
   3. Under the Escalation chain menu, select the escalation chain you created.
   4. Click Save.

   {#event-collection-logicmonitor__substeps_e3w_c3f_mqb}  
   Note:  
   To map the CI to the cmdb_ci_vm_object record instead of the cmdb_ci_server, enable the event rule created for Logicmonitor. The Logicmonitor's collector name, which comes in as a hostname in the payload, should be the same as the object_id of the virtual machine discovered in the cmdb_ci_vm_object record.
{#event-collection-logicmonitor__steps_hbp_nzy_lqb}

*[\>]: and then