---
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


---

# Integrate Sumo Logic events

# Integrate Sumo Logic events {#ariaid-title1}

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

Use the Sumo Logic push connector to integrate Sumo Logic with Event Management by adding a standard webhook in the Sumo Logic
platform.

## Before you begin

Ensure that the Event Management connector's plugin is installed on the ServiceNow AI Platform instance.

Role required: evt_mgmt_integration

## About this task

Configure the Event Management environment for the collection of events from Sumo Logic by authenticating Sumo Logic as a data source. In the Sumo logic site, set your ServiceNow AI Platform instance as the rest endpoint using a webhook.

## Procedure

1. In the Sumo Logic site, create a notification destination.
2. Go to Monitoring and select Custom Webhook.
3. Fill in the form with the Name, Description, and the URL.  
   Use this URL format to push events from Sumo logic to the ServiceNow
   Instance .https://\<username\>:\<password\>@\<instance-name\>.service-now.com/api/sn_em_connector/em/inbound_event?source=sumologic  
   Note:  
   Use a credential having the evt_mgmt_integration role as the username and password.

   In the Payload section, use the following template:

       {
           "type": "{{MonitorType}}",
           "node": "{{ResultsJSON._sourceHost}}",
           "metric_name": "{{Name}}",
           "description": "monitor Query: {{Query}}\n Trigger Condition:{{TriggerCondition}}\n Trigger Value:{{TriggerValue}}\n Trigger Time Range:{{TriggerTimeRange}}\n View Trigger Query:{{TriggerQueryURL}}\n View Monitor:{{QueryURL}} \n Results:{{ResultsJSON}}",
           "name": "{{Name}}",
           "short_description": "{{Description}}",
           "MonitorType": "{{MonitorType}}",
           "Query": "{{Query}}",
           "QueryURL": "{{QueryURL}}",
           "ResultsJson": "{{ResultsJson}}",
           "NumQueryResults": "{{NumQueryResults}}",
           "Id": "{{Id}}",
           "DetectionMethod": "{{DetectionMethod}}",
           "TriggerType": "{{TriggerType}}",
           "TriggerTimeRange": "{{TriggerTimeRange}}",
           "time_of_event": "{{TriggerTime}}",
           "TriggerCondition": "{{TriggerCondition}}",
           "TriggerValue": "{{TriggerValue}}",
           "TriggerTimeStart": "{{TriggerTimeStart}}",
           "TriggerTimeEnd": "{{TriggerTimeEnd}}",
           "SourceURL": "{{SourceURL}}",
           "alertResponseUrl": "{{alertResponseUrl}}"
         }

   Log Monitors Type events can be created without CI binding since you're
   receiving the node value as "node": "{{ResultsJSON._sourceHost}}" in the
   event payload from Sumo Logic. You can create events but you can't bind them
   since you don't get them as host names for the log monitor type. A push
   connector parameter was created - "create_log_monitorType_events" with a
   value of False. If the param value is False, the payload is ignored, and
   "log" events aren't created. If you change the param to True, events are
   created, and then you must define event rules for CI binding.

   Refer to the following ServiceNow Severity Mapping with
   Sumo logic TriggerType table:
   {#sumologic-events-integration__table_yfk_j5p_yvb__entry__2}

   | Sumo Logic Trigger Type | Severity |
   |-|-|
   | Critical | Critical |
   | Warning | Minor |
   | MissingData | Warning |
   | ResolvedCritical/ResolvedWarning/ResolvedMissingData | Clear |
   [Table 1. Severity Mapping]

   {#sumologic-events-integration__table_yfk_j5p_yvb}
* **[Integrate Sumo Logic with REST API key token](https://servicenow-prod.fluidtopics.net/WodMzED8kEayN9w9shSWeA)**   
  Integrate using an API key to establish secure communication and automate data exchange via REST API. This simplifies integration, enabling seamless access to services and enhancing operational efficiency.