What should I know about telemetry data collection?

Data collection prerequisites

NSP has the following prerequisites for telemetry data collection.

• The NEs from which you want to collect data must be discovered, managed, and reachable by the NSP.

• If you want to use a telemetry subscription to manage data from NEs managed by NFM-P, statistics collection must be configured in the NFM-P.

• All required NE adaptors and telemetry custom resources must be installed on the NSP server; see the adaptor documentation.

• If you want to use statistics for Analytics reports with granularity other than raw data, you need aggregation rules for the telemetry types you want to collect; see the Telemetry tutorial on the Network Developer Portal

• You need to configure the aggregation time zone.

• To collect accounting statistics, an FTP mediation policy must be assigned to the NE. FTP mediation policies are created and assigned using a REST API; see the LSOM Framework and APIs tutorial on the Network Developer Portal.

Subscriptions are automatically created for Baseline Analytics, NSP Indicators, and OAM testing. To collect statistics for another purpose, create a subscription and set its state to enabled.

RESTCONF APIs are available for telemetry collection and aggregation; see the Network Assurance API documentation on the Network Developer Portal.

Data storage

You can enable database storage for MDM managed NEs as part of subscription creation. By default, the data collected is stored in Postgres unless there is an auxiliary database enabled, in which case all collected data is stored in the auxiliary database. For NFM-P collected SNMP or accounting statistics, the database parameter in the subscription is ignored.

If gRPC telemetry is enabled on a classic device, known as dual management, the gRPC statistics are stored in the database.

Historical data, that is, data that is stored in a database, is retained according to the age-out policy; see How do I edit an age-out policy?.

Note: For statistics to be available to the Analytics application for aggregated reports, they must be stored in the auxiliary database.

The Telemetry data API also provides the functionality to subscribe, stream, and plot historical and real-time data; see Use Case 5 in the Telemetry Collection tutorial on the Network Developer Portal.