Step 3: Enabling Data in Crosswork Assurance

This article outlines how to stream data to Crosswork Assurance.

Data Flow

Once the Sensor Collector, the Telemetry Collector, and the router telemetry configuration are set up and running, data will begin to flow to the Crosswork Assurance.

No objects will be created in the inventory until the configured ingestion step (below) is completed. This confirms which metrics are to be ingested for each object in the Crosswork Assurance inventory.

Configuring Ingestion

Before a metric of a given object type can be consumed and persisted in Crosswork Assurance, it must be enabled for ingestion in the UI.

To configure ingestion:

1. From Crosswork Assurance, go to Settings ▶ Ingestion.
   This page allows you to select which metrics to ingest for a given object type.

2. Locate the required object type in the left-hand scroll bar. For Cisco Telemetry Collector metrics, they will be the "Cisco Telemetry” category. Example: cisco-telemetry-xr-interface.
   Once the Object type has been selected, all available metrics that have been discovered will be visible.

3. Toggle on your required metrics.
   Once you have toggled on the metrics to enable ingestion, the objects that represent the router telemetry (interface, policy, environment, IPSLA, DMM, and SLM) will appear in the inventory.

You have successfully built a data ingestion pipeline for your default telemetry metrics.

Viewing Telemetry Data in Crosswork Assurance

To view the telemetry metrics that are being streamed out of the Cisco IOS-XR router

1. From Crosswork Assurance, go to Inventory > Sessions.

2. Locate the object of interest using the search bar or by applying type filters. Once located, select the object to access its telemetry metrics.

Tip: All telemetry streaming from the device will appear in Crosswork Assurance. For example, there will be an interface object for every physical and virtual interface on the device. If your use case requires only a subset of objects appear in Crosswork Assurance, a SessionFilter API call can be leveraged to ensure that only specified Interfaces are ingested (as opposed to ingesting all interface metrics on the router).