---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Configure the SolarWinds metrics connector instance

# Configure the SolarWinds metrics connector instance {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Configure the SolarWinds connector instance to receive Metric Intelligence raw data from the SolarWinds server.

## Before you begin

To activate metric collection, ensure that the MID Server that retrieves metrics is configured with the Metric Intelligence extension and that the extension is in Started mode. See [Manually configure the Metric Intelligence extension](https://www.servicenow.com/docs/jSQiQOK0Sw4toJsDuB5N9g "Configure the MID Server Metric Intelligence extension to enable the MID Server to pull raw metrics from external systems, to detect anomalies and report anomalies to the instance along with raw data. This MID Server Metric Intelligence extension is required and must be running in order for your system to be able to collect Metric Intelligence data.").

Configure the Service graph connector for SolarWinds. This is configured in the instance and discovers SolarWinds CIs. For details on configuring this connector, see [Service Graph Connector for SolarWinds](https://www.servicenow.com/docs/access?context=cmdb-integration-solarwinds&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

Role required: evt_mgmt_admin

## About this task

By default, the Solarwinds Metric Connector Collects metrics from the following tables:

* Orion.CPULoad
* Orion.NPM.InterfaceTraffic
* Orion.VolumePerformanceHistory
* Orion.VolumeUsageHistory
* Orion.ResponseTime
{#configure-solarwinds-connector__ul_ffk_fr3_dcc}

## Procedure

1. Navigate to Event ManagementIntegrationsConnector Instances.
2. Select New and create a connector instance.  
   For details on the connector instance fields displayed on the page, see [Solarwinds connector instance form](https://www.servicenow.com/docs/zPQOwg2oFW6WStBNjVOQmg "The Solarwinds connector instance form displays the fields you must fill in when creating a Solarwinds connector instance.").
3. Select and hold (or right-click) the form header and select Save.  
   The connector instance values are added to the form and the parameters that are relevant to the connector appear.
4. **Optional:** In the Connector Instance Values section, you can edit the values of the mandatory SolarWinds parameters.  
   For details on the connector instance value parameters, see [Solarwinds connector instance value parameters](https://www.servicenow.com/docs/hitEehTQmfSQRETkTQxDIQ "The following table displays the Solarwinds connector instance value parameters that you can fill in, as needed, when creating a Solarwinds connector instance.").
5. In the MID Servers for Connectors section, add a MID Server for the SolarWinds connector to use.
6. In the Related Links section, select Configure metrics to collect.  
   Only metrics with the value Active=true are collected by the instance.
7. Configure the metrics you want the instance to collect with the value Active=true.  
   Metrics with the value Active=false are not collected by the instance.
8. **Optional:** Select New to create new metrics.  
   Configure the fields on the Connector instance metrics - New record (sn_em_connector_instance_metrics_solarwinds) page.{#configure-solarwinds-connector__table_m2c_jnz_zbc__entry__2}

   | Field | Description |
   |-|-|
   | Metric name | Display name for the metric to be configured in the ServiceNow instance. |
   | Metric connector instance | Set by default to SolarWinds connector instance. All metrics are collected for the SolarWinds connector instance. |
   | Additional columns | List of additional columns to fetch for CI-related information. For example: DateTime, Node, Resource. If DateTime is not provided, the current time is used as the metric timestamp. If Node and Resource are provided, they are populated accordingly. To reference fields from a parent table, use dot-walking format, such as `Interface.InterfaceName`. If a field should populate a specific standard field (like Resource), use an alias with the same name. For example, to use `InterfaceName` as the resource, specify it as `Interface.InterfaceName AS Resource`. |
   | Table Name | Name of the table from which metrics are collected. |
   [Table 1. Connector instance metrics page - New record]

   {#configure-solarwinds-connector__table_m2c_jnz_zbc}
   * Ensure that the CIs related to the metrics exist in the instance.
   * Create an event rule to perform CI binding, as needed. For details, see [Create or edit an event rule](https://www.servicenow.com/docs/S0ulPjfvh7Pz7phgkfVYFw "You can create event rules to generate alerts for tracking and remediation. Use team-based integrations in event rules to make sure that connector ownership and execution of rules give precedence to general rules. Teams can maintain consistency and hierarchy while offering flexibility and customization options.").
   {#configure-solarwinds-connector__ul_mmd_m4z_zbc}
9. Select Test Connector to verify the connection between the MID Server and the connector.
10. After a successful test, select the Active check box and then select Update.  
    Note:  
    Ensure that Registration Mode is enabled for the SolarWinds source in the Metric Sources table.
{#configure-solarwinds-connector__steps_ik1_ffx_t2c}

*[\>]: and then