NSP Data Collection and Analysis functions provide collection, processing, and analysis for MDM and Cloud Native (CN) telemetry. NSP supports configuring telemetry subscriptions and using baseline analytics, NSP indicators, and OAM tests for anomaly detection, metric customization, and network tests.

The type and scope of statistics support are dependent on the NE source. NSP supports the following telemetry providers:

• MDM-based telemetry

• Cloud Native telemetry

• Statistics collection for classically managed NEs

The following table provides definitions of telemetry terms in use in NSP.

Note: This table reflects the function of Release 24.11 artifacts. If you are using adaptor artifacts from previous releases, telemetry functions are supported at the level of the release your adaptor artifacts are for; see the artifact guide for the adaptor artifacts you are using.

Term	Definition	References	Notes
Telemetry providers
MDM telemetry	Collection using SNMP for multivendor NEs and for model-driven NEs using artifacts from releases prior to 23.8.	See the artifact guide for the NE type and NSP release.	Contact Nokia for information about third-party NE adaptors that may not be commercially available.
Cloud Native telemetry (CN telemetry)	Collection using gNMI for Nokia and multivendor NEs gNMI uses gRPC as the underlying protocol, with the NSP MDM server acting as the gRPC client, and the NE acting as the gRPC server.	For information about using NSP for cloud native telemetry, see the chapters in this document. For information about using APIs for cloud native telemetry, see the Telemetry tutorial on the Network Developer Portal.	Cloud native telemetry requires a GRPC mediation policy in the discovery rules used to discover and manage the NEs. The client/server gRPC communication must be authenticated and encrypted.
Telemetry for classically managed NEs	Collection using SNMP for Nokia classically managed NEs	For more information about statistics management using the NFM-P, see the NSP NFM-P Statistics Management Guide.	—
Related terms
Vendor agnostic (va)	Telemetry definitions included with the NSP that allow for collection of statistics on multiple NE types.	For information about the telemetry definition bundles for a specific model-driven NE type, see the artifact guide for the NE type. See the API Documentation on the Network Developer Portal to find the list of applicable telemetry definitions. For information about installing telemetry artifacts, see How do I install telemetry artifacts?.	The vendor agnostic telemetry bundle for an NE includes telemetry mappings for the NE that align with the telemetry definitions packaged with the NSP.
Device telemetry	Device-specific telemetry, including both YANG telemetry definition files and device adaptation custom resources for CN telemetry.		The device telemetry bundles for an NE contain telemetry definitions and adaptation for the supported NE-specific counters.
Accounting telemetry	Collection of accounting files using cloud native telemetry		The accounting file bundle for an NE contains telemetry mappings for accounting collection on the NE. Accounting collection uses the FTP/SFTP protocol. It requires a file transfer mediation policy in the discovery rules used to discover and manage the NEs.

NSP provides the following using collected telemetry data:

• visualization— showing information in the form of telemetry charts

• aggregation—combining measurements for analysis by Analytics

  For aggregation information to be available, the auxiliary database must be installed.

• baseline analytics and anomaly detection—defining trends using telemetry data and identifying outliers

• NSP indicators—defining and tracking KPIs using customized metrics

• OAM tests—creating tests using templates

The telemetry functions described in this document are distinct from:

• Cflowd AA statistics and other flow statistics collected via Flow Collectors

• Analytics report catalogs, although statistics collected using DCA aggregation functions are available in Analytics. See the NSP Analytics Report Catalog for information about report generation and visualizations, and reference lists of the available report catalogs. Baseline analytics and analytics reporting are different functions, each with their own installation options.

Telemetry artifacts

The telemetry types for NEs are defined using YANG files in the NE artifact bundles. NSP uses custom resource (CR) definitions to translate the YANG data, map incoming telemetry to managed objects in the network, and output data to PostGres, Vertica, and Kafka as required. These resource definition files can be viewed as part of the artifact archive. For information about the CRs that accompany your NE adaptors, see the relevant artifact guide.

See How do I install telemetry artifacts? for more information.

Note: You must install the relevant adaptors before managing the associated NE types to use the telemetry definitions. NSP also includes a limited, generic set of default telemetry. Without installing adaptors, you will only see the default telemetry.

Telemetry subscriptions

A subscription defines the parameters of telemetry collection and uses a filter definition to select the NEs/objects. NSP deploys the specified data to the NE and registers the Kafka subscription, which is used to transfer telemetry data from the NE to NSP.

See What is a subscription? for more information.