RemcoLengers
ServiceNow Employee

How to Connect LogicMonitor to ServiceNow Event Management Using the Built-In Connector

 

ServiceNow ships an out-of-the-box Event Management Connector for LogicMonitor. This guide walks you through the end-to-end setup — from activating the connector in ServiceNow to receiving your first events.

 

## Prerequisites

 

On your ServiceNow instance:

 

- The **Event Management** plugin (`com.glideapp.itom.snac`) installed and activated.
- The **Event Management Connectors** plugin (`sn_em_connector`) installed and activated.

 

On the LogicMonitor side, you need admin access to create integrations and escalation chains.

 

Step 1: Activate the LogicMonitor Connector in ServiceNow

 

Navigate to the "Service Operation Workspace"
 
 RemcoLengers_1-1778591093231.png

 

This assumes you have the latest ITIOM AIOps configuration center installed: "Add integration"

 

RemcoLengers_2-1778591268333.png

 

 Search for "Logic Monitor" and this give you the option to use an integration direct to the instance or via a MID server. If there is high event volume MID server is the preferred route.
RemcoLengers_0-1778591050475.png


Fill out the field and activate and save. This will enable the URL to be used in LogicMonitor

RemcoLengers_0-1778591510291.png

 

The tile gives you a pre-built inbound event URL:

 

`https://<instance>.service-now.com/api/sn_em_connector/em/inbound_event?source=logicmonitor&sys_id=<connector_sys_id>`

 

Copy that URL — you'll need it in Step 3.

 

Step 2: Get the JSON Payload Template

 

The connector comes with a ready-made JSON payload template that maps LogicMonitor alert tokens to ServiceNow event fields. You'll find it by navigating to **Event Management > Push Connectors** and opening the **LogicMonitor Push Connector** record. The template is in the **Description** field:
 
RemcoLengers_0-1779351239207.png

 

{
"type":"##ALERTTYPE##",
"status":"##ALERTSTATUS##",
"level":"##LEVEL##",
"host":"##HOST##",
"datasource":"##DATASOURCE##",
"eventsource":"##EVENTSOURCE##",
"batchjob":"##BATCHJOB##",
"group":"##HOSTGROUP##",
"datapoint":"##DATAPOINT##",
"start":"##START##",
"end":"##END##",
"duration":"##DURATION##",
"date":"##DATE##",
"value":"##VALUE##",
"threshold":"##THRESHOLD##",
"message":"##MESSAGE##",
"alertid":"##ALERTID##"
}
Copy this entire JSON block. The `##TOKEN##` placeholders are LogicMonitor's alert token syntax — they get replaced with actual alert values at runtime. This ensures the ServiceNow Push Connector Listener Script can parse the incoming events correctly.

 

Step 3: Configure the Custom HTTP Delivery in LogicMonitor

 

In your LogicMonitor portal:

 

1. Go to **Settings > Integrations** and click **Add > Custom HTTP Delivery Integration**.
RemcoLengers_1-1779351630335.png

 

2. Give it a **Name** (e.g., "ServiceNowEventManagement") and a **Description**.
3. Check **Use the same URL and data to notify on various alert activity**.
4. Select which alert activities should fire a notification: **Acknowledged**, **Cleared**, and **Escalated/De-escalated** as needed.
5. Set the HTTP method to **HTTP POST**.
6. Enter the **URL** you copied from the ServiceNow connector tile in Step 1.
7. Fill in **Username** and **Password** — this is a ServiceNow account with the `evt_mgmt_integration` role. Basic Authentication is used. The user need the "evt_mgmt_integration" Role in ServiceNow.
8. Under Alert Data, select **Raw** and set the format to **JSON**.
9. Paste the JSON payload template from Step 2 into the body field.
10. Click **Test Alert Delivery** to verify, then **Save**.
RemcoLengers_2-1779353437527.png

 

RemcoLengers_3-1779353476963.png

 

If successfully sending the Event into ServiceNow, it will look like this:

RemcoLengers_4-1779353514127.png

 

You can see the incoming test event in the Connector setup under "Events"

RemcoLengers_5-1779353635881.png

 

Now you have the integration working and there rest is LogicMonitor configuration on when to send Events into ServiceNow.

 

Step 4: Create an Escalation Chain in LogicMonitor

 

The integration fires when an escalation chain triggers it.

 

1. Go to **Settings > Alert Settings > Escalation Chains** and click **Add**.
2. Name it (e.g., "ServiceNow Events").
3. Under **Stages**, add a stage Select the User and select the Custom HTTP Delivery integration you just created as the Contact Method.
4. Save.
 
RemcoLengers_6-1779353917614.png

 

 

Step 5: Create Alert Rules in LogicMonitor

 

1. Go to **Settings > Alert Settings > Alert Rules** and click **Add**.
2. Configure the conditions that should route alerts to ServiceNow.
3. Under **Escalation chain**, select the chain you just created.
4. Save.

 

## Verification

 

Fire a test alert in LogicMonitor (or wait for one). In ServiceNow, check **Event Management > All Events** — you should see inbound events with source `logicmonitor`. From there, standard Event Management processing takes over: event rules, alerts, and service mapping.
 
1 Comment
Jim Palmer
ServiceNow Employee

Some additional information (since I'm in the middle of this right now)

The LogicMonitor alert tokens are available here: https://www.logicmonitor.com/support/logicmodules/about-logicmodules/tokens-available-in-logicmodule...

You can include any number of token values and they'll be included in the [additional_info] field in the [em_event] table - really useful for event binding.

 

The pull connector (this is for the webhook based push) does not retrieve alerts from LogicMonitor, it's used exclusively for sending ACKs from the alert back to LogicMonitor via the API with the [bi-directional=true] boolean. There's an open case about the scripting for the pull connector including how the connector instance and MID script assume the [host] field on the connector instance only contains the logicMonitoring instance name (not the IP or fqdn) and how it uses the [message_key] as the LogicMonitor alert ID.
So OOTB this callback doesn't really support multiple LogicMonitor instances (as the ID can be duplicated). And if you alter the [message_key] in event rules to make the event more unique, the OOTB callback will not work.