--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Configure a push connector # Configure a push connector {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Configure a push connector This guide explains how to configure listeners and connectors in ServiceNow Event Management to push event information either directly to the instance or through a MID Server. Event Management supports event ingestion via push connectors or scripts, with configuration required for all methods except scripted event collection. Show full answer Show less To enable push connector integration, you must install the Event Management Connector plugin from the ServiceNow Store. ## Key Steps * **Create an integration user:** Follow user creation procedures and assign the `evtmgmtintegration` role. Ensure the user's Identify Type is set to **Machine**. * **Use the standard event form:** All incoming events must conform to a standard event format regardless of their source to ensure consistent processing. ## Event Collection Modes and Connectors Event Management supports multiple event collection methods, including pre-built listeners and connectors, custom listeners, and various protocols: * **Provided by base system:** Includes connectors for AWS CloudWatch, Azure Monitor, BMC TrueSight (legacy and v2), Datadog, Dynatrace, Google Cloud Platform, New Relic, and generic event collection via MID Server or instance. * **MID WebService:** Configure MID WebService Event Collector to push events to the MID Server. * **Custom listeners:** Create your own listeners via MID WebServer API or custom transformation scripts. * **SNMP:** Use generic SNMPv2 listeners or build custom SNMP listeners to collect trap events. * **Email:** Configure email listeners to collect events sent by email. ## Practical Benefits for ServiceNow Customers By configuring push connectors, ServiceNow customers can efficiently ingest events from diverse external sources and protocols, enabling real-time monitoring and automated event processing within Event Management. This flexibility supports seamless integration with existing monitoring tools and custom event sources, improving incident response and operational insight. You can configure listeners and connectors to push event information to the instance or MID Server. Event Management receives external events through a push connector or script. If you are using a script to collect events, no configuration is required. All other methods of collecting events require configuration. After event collection configuration, Event Management can collect events that are sent directly to the instance, or via the MID Server, SNMP trap, or email. Note: Integrating with push connectors is only available by installing the Event Management Connector plugin from the ServiceNow Store. ## Create integration user {#push-event-listener__section_fsc_sgw_ckc} Follow the steps in [Creating users](https://www.servicenow.com/docs/access?context=ua-creating-users&version=australia&pubname=australia-platform-administration&ft:locale=en-US) to create a user and grant the \[evt_mgmt_integration\] role to the user. Note: Verify that the Identify Type of the user is Machine. ## Standard event form All events must use a standard event form, regardless of how they arrive at the instance. For more information, see [Event field format for event collection](https://www.servicenow.com/docs/lJU_U2pD_SsT2SnoxdhPIA "Event Management requires all events to use a standard form, regardless of how they arrive at the instance."). ## Event collection Event Management facilitates communication and movement of data between external applications, data sources, services, and the ServiceNow AI Platform instance.{#push-event-listener__simpletable_av2_cxd_gz__entry__2} | Event collection modes | Description | |-|-| | Provided by the base system | Listeners and connectors provided with the Event Management application: * AWS CloudWatch, see [Integrate AWS platform as a data source](https://www.servicenow.com/docs/kU9hZ7X3HA6tCOFHXdZZlQ "Integrate Amazon Web Services (AWS) with Event Management. To add AWS platform as a data source, configuration is required in the AWS platform."). * Azure event messages, see [Integrate Azure Monitor as an authenticated data source](https://www.servicenow.com/docs/nvSoG0eEh_JbGrMI4J5_yA "Integrate Microsoft Azure with Event Management by adding the Azure Monitor as an authenticated data source."). * BMC TrueSight events, see [Event collection from BMC TrueSight and BMC TrueSight_v2](https://www.servicenow.com/docs/BUS~WinaEUBrf1wcnluTVQ "The MID WebService Event Collector enables you to collect JSON formatted event messages sent from BMC TrueSight Operations Management (TrueSight), previously known as BMC ProactiveNet Performance Management (BPPM), utilizing event stream notification capabilities."). * Datadog events, see [Integrate Datadog platform events](https://www.servicenow.com/docs/B~njB46ElZHYew6XPgg_TA "Integrate Datadog with Event Management by adding a standard webhook in the Datadog console."). * Dynatrace events, see [Integrate Dynatrace platform events](https://www.servicenow.com/docs/vhXAAnGQXw_uqnp~V_lBDg "Integrate Dynatrace with Event Management by adding Dynatrace as an authenticated data source."). * Google Cloud Platform (GCP) events, see [Integrate Google Cloud Platform (GCP) events](https://www.servicenow.com/docs/_iPdPYbfPi~vyw1SNXA4Jg "Integrate Google Cloud Platform (GCP) with Event Management by adding a standard webhook in the GCP console.") * New Relic events, see [Integrate New Relic platform events](https://www.servicenow.com/docs/MgT7us_BYBcG9qj2qzE~Vg "Integrate New Relic with Event Management by adding a standard webhook in the New Relic old and new consoles."). * Generic event collection through the MID Server. * Generic event collection through the instance. {#push-event-listener__ul_bvm_qrl_gz}Where event messages are received in XML, you can base your script on the example XML transform script provided with the base system. | | Via MID WebService | You can configure the MID WebService Event Collector to push event messages to the MID Server. For more information, see [Pushing events to the MID Server using web service API](https://www.servicenow.com/docs/SKOH0YMs7OBcYrcymOFyAw "Configure the MID WebService Event Collector to provide a URL method to push event messages to the MID Server."). | | Create your own content | You can configure your own listener: * Via MID WebServer API. See [Pushing events to the instance using web service API](https://www.servicenow.com/docs/iLiXUWd9WH27soFTKn4ZvQ "You can use a web service interface, supported by ServiceNow, that operates on the JSON object as the data input and output format."). * Via Custom Transformation. See [Event collection from custom payloads](https://www.servicenow.com/docs/XKkWORGlBYkHglpx_TPQMg "The MID WebService Event Collector enables you to collect event information from custom payloads in JSON, XML, or plain text format."). {#push-event-listener__ul_j1r_1sl_gz} | | Via SNMP | SNMP listeners provided with the Event Management application: Generic SNMPv2. See [Configure event collection for SNMP traps](https://www.servicenow.com/docs/claVcnNwSd74ppwjzoRpCw "The SNMP listener runs on the MID Server, which acts as a collection endpoint for SNMP traps. The MID Server sends the traps to the ServiceNow instance for further processing as an event by Event Management."). In addition, you can create your own custom listener. See [Integrate with push connectors](https://www.servicenow.com/docs/A7TVlbF~vQvO01HFJd0W1w "Integrate with a push connector to connect to an external event source. Push connectors process the collected event messages and transform them to the required event format."). | | Via Email | Email listener. See [Configure event collection from email](https://www.servicenow.com/docs/hhbdukuM6ddXyEM7ECodVw "Configure an inbound email action to send email notifications when events and alerts are triggered."). | [ ] {#push-event-listener__simpletable_av2_cxd_gz} **Related reference** * [Push connector instance form](https://www.servicenow.com/docs/k9sIrIY9DW4rRwBBWAKzpA "Push Connector Instance form displays the fields that you must fill when you create or modify a connector.")