---
sourceDocument: Brazil Telecommunications Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-service-ops

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Configure a metric pull connector

# Configure a metric pull connector {#ariaid-title1}

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure metric pull connectors to retrieve performance data from external management systems such as Meraki, Fortinet, or VeloCloud.

## Before you begin

Role required: TSOM Assurance admin

## Procedure

1. Navigate to WorkspacesService Operations Workspace.
2. From the navigation pane, select the Integrations Launchpad icon ![]().
3. Select the Browse Integrations tab
4. Search for the external management system integration (for example, Meraki, Fortinet, or VeloCloud).
5. Select the integration tile labeled Metrics.
6. On the Connector Instance New record page, in the Name field, enter a unique name for the connector type.
7. In the Connector definition field, select the type of integration you're setting up.
8. **Optional:** In the Description field, enter brief information about this connector.
9. **Optional:** In the Assignment group field, select the group or team responsible for managing and maintaining the connector.
10. In the Host IP field, enter the IP address or host name used to select the appropriate MID Server for communicating with the event source host.
11. In the Credential field, select the valid credentials to access the event source host.
12. In the Metrics collection schedule (seconds) field, enter the polling interval for metric collection.  
    Important:  
    For a device performance (CPU usage) connector instance, if you enter a value below 1800 seconds (30 minutes), the system automatically resets the schedule to 1800 seconds and displays a message. For a Fortinet interface logs connector instance, if you enter a value above 600 seconds (10 minutes), the system automatically resets the schedule to 600 seconds and displays a message. In both cases, the record saves successfully. This enforcement applies only when a numeric value is entered; an empty or blank field bypasses it.
13. **Optional:** Validate the connectivity of the connector before activating it by selecting Test Connector.
14. Select Update.
15. **Optional:** Verify that the pull connector is configured correctly and events are flowing into the system by returning to the Integrations Launchpad.  
    The tiles appear under the Installed Integrations tab.
{#configure-an-event-pull-connector__steps_srm_zfk_5wb}
**Related reference**   

* [Arista VeloCloud installed integrations](https://www.servicenow.com/docs/B6kL5KoKktKWOV1k4cyE2Q "Predefined system integrations use VeloCloud REST APIs to pull events into your ServiceNow instance to monitor your Arista VeloCloud devices.")
* [Cisco Meraki installed integrations](https://www.servicenow.com/docs/AsWHLTszOMsOESA9fQL7Ag "Predefined system integrations use Meraki REST APIs to pull metric data into your ServiceNow instance to monitor your Cisco Meraki devices. Each integration is driven by a connector instance whose metric parameter determines the data that the instance collects.")
* [Fortinet installed integrations](https://www.servicenow.com/docs/vl5~3ZTiQos6nRN7~iez4A "Predefined system integrations use Fortinet REST APIs to pull metric data into your ServiceNow instance to monitor your Fortinet devices.")  
**Related topics**   

* [Exploring Metric Intelligence](https://www.servicenow.com/docs/access?context=exploring-metric-intelligence&version=brazil&pubname=brazil-it-operations-management&ft:locale=en-US)

*[\>]: and then