Telemetry Ingestion Solution Architecture

Solution Architecture

First, before you configure telemetry ingestion, this article provides an overview of the components involved, and explains how the solution works.

The Telemetry Collector receives and ingests a default set of sensor path telemetry metrics that are being streamed out of the IOS XR and IOS XE devices on a user-defined cadence.

The Telemetry Collector transforms the data to OpenMetrics format and transmits the data to the Sensor Collector, the data collector component for Provider Connectivity Assurance. The Sensor Collector securely transmits the data to Provider Connectivity Assurance in the cloud.

For the out-of-the-box default Telemetry collection, the router is configured for MDT dial-out connectivity to the Telemetry Collector and is set up to stream the telemetry at whatever cadence is specified on the router (every 1 minute or every 5 minutes, for example). As shown in the diagram, this cadence is the interval at which the data will appear in Provider Connectivity Assurance. If gNMI dial-in is the preferred connectivity approach, that configuration can be achieved via API calls.

In scenarios where the out-of-the-box IOS device metrics are not sufficient, customization of the Telemetry Collector and Sensor Collector can be quoted by CX or Partners. At its core, the Telemetry Collector integrates Telegraf within it. This architecture allows CX or Partners to customize it for specific use cases.

Contact Sales if additional customization is required to augment the default IOS XE and IOS XR with additional sensor paths, metrics, metadata ingestion, or if an entirely different data source is required.