Configure a MID Server push listener for event collection

task australia Updated Sep 10, 2026 2 min read configure-midserver-event-collection.md

The MID Server supports the collection of event messages using the MID Web Server to collect data from external sources. The data is transformed (parsed) to the format required for event fields in the event [em_event] table and transmitted to the instance.

Before you begin

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

Role required: evt_mgmt_admin

About this task

The MID Web Server extension enables external clients to push metric data and events to the MID Server. See Configure the MID Web Server extension. Use the MID WebService Event Collector to enable a URL method to push event messages to the MID Server. See Configure the MID WebService Event Collector Context.

Configure a MID Server with either EventManagement or All in the Supported Applications List.

To ensure uninterrupted services, consider also configuring a failover MID Server cluster.

Procedure

Navigate to All > MID Server > Servers.
Double-click the MID Server that you want to configure, or click New to create a new MID Server.
In the Supported Applications section, click Edit.
1. Click Edit.
2. In the slushbucket, either select Event Management or ALL and click the > add button.
3. Click Save.
To ensure that the MID Server is validated, under Related Links, select Validate.

For more information, see Validate a MID Server.
Click Update.

What to do next

Configure the MID WebService Event Collector to enable a URL method to push event messages to the MID Server. For more information, see Configure the MID WebService Event Collector Context.

Configure the MID Web Server extension

Configure the MID WebService Event Collector Context

67 lines · 3.9 KB Wrap lines

---
title: Configure a MID Server push listener for event collection
description: The MID Server supports the collection of event messages using the MID Web Server to collect data from external sources. The data is transformed \(parsed\) to the format required for event fields in the event \[em\_event\] table and transmitted to the instance.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/event-management/configure-midserver-event-collection.html
release: australia
product: Event Management
classification: event-management
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Configure a push connector, Configure Event Management connectors, Event Management Integrations, Configure, Event Management, ITOM AIOps, IT Operations Management]
---

# Configure a MID Server push listener for event collection

The MID Server supports the collection of event messages using the MID Web Server to collect data from external sources. The data is transformed \(parsed\) to the format required for event fields in the event \[em\_event\] table and transmitted to the instance.

## Before you begin

Ensure that the Event Management Connectors \(sn\_em\_connector\) plugin is installed on the ServiceNow AI Platform instance.

Role required: evt\_mgmt\_admin

## About this task

The MID Web Server extension enables external clients to push metric data and events to the MID Server. See [Configure the MID Web Server extension](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-mid-web-server-extension.md). Use the MID WebService Event Collector to enable a URL method to push event messages to the MID Server. See [Configure the MID WebService Event Collector Context](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-em-context-extension.md).

Configure a MID Server with either **EventManagement** or **All** in the Supported Applications List.

To ensure uninterrupted services, consider also configuring a failover MID Server cluster.

## Procedure

1. Navigate to **All** &gt; **MID Server** &gt; **Servers**.

2. Double-click the MID Server that you want to configure, or click **New** to create a new MID Server.

3. In the **Supported Applications** section, click **Edit**.

1. Click **Edit**.

2. In the slushbucket, either select **Event Management** or **ALL** and click the **&gt;** add button.

3. Click **Save**.

4. To ensure that the MID Server is validated, under Related Links, select **Validate**.

For more information, see [Validate a MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_ValidateAMIDServer.md).

5. Click **Update**.

## What to do next

Configure the MID WebService Event Collector to enable a URL method to push event messages to the MID Server. For more information, see [Configure the MID WebService Event Collector Context](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-em-context-extension.md).

**Related topics**

[Configure key-based MID Web Server authentication](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-mid-web-server-extension-metric-data.md)

[Configure the MID Web Server extension](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-mid-web-server-extension.md)

[Configure the MID WebService Event Collector Context](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-em-context-extension.md)