Telecommunications Service Operations Management reference

reference australia Updated Sep 10, 2026 3 min read components-installed-with-tsom.md
Raw file servicenow.com

Several types of components are installed with Telecommunications Service Operations Management applications and plugins.

  • Arista VeloCloud installed integrations
    Predefined system integrations use VeloCloud REST APIs to pull events into your ServiceNow instance to monitor your Arista VeloCloud devices.

  • Fortinet installed integrations
    Predefined system integrations use Fortinet REST APIs to pull metric data into your ServiceNow instance to monitor your Fortinet devices.

  • Fortinet extension points reference
    The Service Graph Connector for Fortinet exposes nine scripted extension points that let you customize specific parts of the connector's behavior without modifying the shipped application. Use this reference to find which extension point controls the behavior you want to change.

  • Cisco Meraki installed integrations
    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.

  • System components installed with Telecommunications API notifications
    Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the ServiceNow system.

  • System components installed with Nokia Altiplano
    System properties control how the connector operates, including discovery options and performance settings.

  • Telecom discrepancy identification and reconciliation
    The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin enables the TSOM Visibility applications. It contains logic shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.

  • Fortinet Service Graph Connector API endpoints
    The Service Graph Connector for Fortinet integrates Fortinet Dashboard API data into ServiceNow AI PlatformConfiguration Management Database (CMDB). This document details the API endpoints used and how data flows through the system.

  • Cisco Meraki Service Graph Connector API endpoints
    The Service Graph Connector for Meraki integrates Cisco Meraki Dashboard API data into ServiceNow AI Platform®Configuration Management Database (CMDB). This document details the API endpoints used and how data flows through the system.

  • Cisco Meraki extension points
    Each Meraki extension point controls one part of the connector's data collection. Use these tables to find the handler that governs the behavior you want to change and the arguments it receives.

  • Arista VeloCloud Service Graph Connector API endpoints
    The Service Graph Connector for Arista VeloCloud integrates VeloCloud Orchestrator API data into ServiceNow AI Platform Configuration Management Database (CMDB). This document details the API endpoints used and how data flows through the system.

  • MPN Formulas table
    Reference for the MPN Formulas [sn_tsom_em_conns_kpi_definitions] table and the automatic processing that occurs when a record is inserted or updated.

  • MPN latency KPIs
    Reference for the latency KPIs collected by the MPN Pull Connector and the derived UE-to-switch latency metric.

  • https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-service-ops/telecommunications-service-operations-management/nokia-mpn-security-log-fields.md

  • MPN health status rule reference
    Default rule set (version 0.0.11) for calculating health status for MPN radio and core server components, including error codes.

  • Equinix connector metrics
    Reference for the power metrics collected at the cabinet level and the environmental metrics collected at the zone level by the Equinix pull connector.

  • Retrieve data from Nokia Altiplano via REST API
    Examples of Retrieving Data from Nokia Altiplano via REST API.

  • Page limits for Meraki pull connector endpoints
    The Meraki pull connector paginates API requests so that all records are retrieved for large organizations. The page size is set per endpoint to match each endpoint's maximum supported value in the Meraki API v1.

  • Pull connector granularity constraints
    Each connector type enforces minimum and maximum values for the granularity and metrics collection schedule fields on the connector instance form. The connector instance form rejects values outside the supported range.

  • Metric aggregation configuration reference
    The configuration object passed to the metric aggregation scripted extension point defines what to aggregate, how to aggregate it, and where to publish the result. The parameters that apply depend on the aggregation mode.

  • Metric type IDs
    Metric type IDs identify each time-series metric that a connector writes to the metrics database. Use these IDs to locate metrics in Insights Explorer or when you build custom dashboards and indicators.

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