Configure elastic event pull connectors for MPN

task australia Updated Sep 10, 2026 2 min read configure-mpn-connectors-for-events-and-metrics.md
Raw file servicenow.com

Configure a mobile private network (MPN) pull connector instance to collect metrics, including latency KPIs, from specified KPI domains in Elastic data store. The connector publishes metrics for assurance monitoring and analytics.

Before you begin

The MID Server MID Server must have Access Control (ACL) records for each of the following tables:

  • sn_tsom_em_conns_kpi_definitions (KPI definitions table)
  • cmdb_ci_network_service_instance
  • cmdb_ci_app

For more information, see Set up a MID Server role.

Roles required: tsom_assurance_admin and assigned roles for MID Server.

Procedure

  1. Navigate to All > Event Management > Integrations > Connector Definitions.

  2. Select Nokia MPN Pull Connector.

  3. Open an existing connector instance or create one:

    • To use an existing instance, select it from the Connector Instances list and edit only the fields you need to change.
    • To create an instance, select New and complete all required fields as described in the following steps.
  4. On the form, fill in the fields.

    Field Description
    Host IP URL of the MPN host
    Credential Username and password for basic authentication
    kpi_domain identifier Domains to collect metrics from. Leaving the field empty collects metrics from all domains. Entering one or more domain identifiers, with values separated by commas (for example, RAN, Core) collect metrics only from specific domains.
    Metrics collection schedule How long, in seconds, each metrics collection should run.

    Note: Active connector instances also collect the latency KPIs, from a separate Elasticsearch index, on the same metrics collection schedule. For a list of the latency KPIs collected and how the derived KPI is calculated, see the MPN latency KPIs reference.

  5. Add a MID Server.

    1. In the MID Servers for Connectors section, select the plus icon next to Insert a new row.

    2. In the MID Server field, enter the name of the MID Server.

    3. Save your selection by selecting the green check mark.

  6. Enable the connector instance by selecting the Active check box.

    The connector begins collecting metrics from Elastic data store.

  7. Select Update.

Parent Topic:Configure Telecom Assurance

Related topics

MPN latency KPIs

View metric to CI and resource binding

Event field mapping configuration

Create an event rule to bind metric events to host CIs

View metric values in the Insights Explorer

Create an Insights Explorer view

Search documentation
Search document titles and file paths on the australia branch