Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Collect Analytics Data Overview

Paragon Automation Release 21.2 supports collecting analytics data from Juniper Networks devices and Cisco IOS XR devices. Table 1 lists the data that are collected from the Juniper Networks devices and Cisco IOS XR devices.

Table 1: Data Collected for Analytics

Supported on



Collected by Default

Ingest Type

Juniper Networks Device

Cisco IOS XR

Rules Used to Collect Data

Label-Switched Path (LSP) statistics [RSVP, SR (both colored and non-colored)][*





controller-telemetry /ctrl-label-switched-path

controller-telemetry /ctrl-label-switched-path-aggregation

Logical and physical interface statistics


JTI for Juniper Networks devices

OpenConfig for Cisco IOS XR devices



controller-telemetry /ctrl-logical-interface

controller-telemetry /ctrl-logical-interface-aggregation,

controller-telemetry /ctrl-physical-interface

controller-telemetry /ctrl-physical-interface-aggregation

Segment ID (SID)





controller-telemetry /ctrl-sr-sid

Link Latency





controller-telemetry /ctrl-link-latency

LSP Latency


Derived from Syslog



controller-telemetry /ctrl-lsp-latency

Quality of Service (QoS)





controller-telemetry /ctrl-egress-queue-interface

controller-telemetry /ctrl-ingress-queue-interface

Label Distribution Protocols (LDP) demands





controller-telemetry /ctrl-demand-stats


Workflow to Collect Device Statistics

Paragon Automation contains a default controller device group and a default controller playbook. Devices must be added to the controller device group so that analytics data can be collected from them. The controller playbook defines the rules for collecting the analytics data.

The following is the workflow to collect analytics data in Paragon Automation:

  1. If not added already, add the devices from which you want to collect data, to the Controller device group. See Edit a Device Group.

  2. Run the device collection task to correlate the links to the interfaces displayed in the topology view (Network > topology); see Add a Device Collection Task.

  3. For a Juniper Networks device, configure the devices to send JTI telemetry data and RPM statistics; see Configure Routers to Send JTI Telemetry Data and RPM Statistics to the Data Collector.

    For a Cisco IOS XR device, configure OpenConfig for collecting interface statistics.

    To configure OpenConfig on Cisco IOS XR devices:

    1. Access the CLI of the IOS XR device.

    2. Add the following configuration:

    3. Commit the configuration.

  4. Add optional rules to the controller playbook in Paragon Automation.

    The rules for collecting LSP statistics, interface statistics, SID statistics, and link latency are added to the controller playbook by default.

    If you want to collect QoS and LDP demand statistics, you must add the rules for collecting these statistics manually. To add rules to the controller playbook.

    1. Click the Configuration > Playbooks icon in the left navigation menu.

      The Playbooks page appears.

    2. Click the Controller playbook.

      The Edit Playbook Controller page appears.

    3. In the Rules field, click and select the following rules:

      • controller-telemetry/ctrl-egress-queue-interface and controller-telemetry/ctrl-ingress-queue-interface for collecting QoS data.

      • controller-telemetry/ctrl-demand-stats for collecting link delay statistics.

    4. Click Save and Deploy.

      A confirmation message appears that the playbook is successfully saved and deployed on the devices in the controller device group.

      For more details on editing a playbook, see Edit a Playbook

    5. Pause the current playbook instance assigned to the controller device group and add the new playbook instance. see Manage Playbook Instances for details.

    6. (Optional) Delete the paused playbook instance.

  5. Commit the configuration.

  6. Add the following data rollup summarization profiles to the controller device group, if you added rules for LDP demand statistics and QoS data in step 4:

    • ctrl-demand-stats-rollup-profile if you added rule for collecting LDP demand statistics.

    • ctrl-egress-queue-interface-rollup-profile and ctrl-ingress-queue-interface-rollup-profile if you added rule for collecting QoS data.

    controller-default-rollup-profile is added to the controller device group by default.

    For details about data summarization profiles, see Data Summarization Overview and Apply Data Summarization Profiles.

  7. Add devices to the collector device group to enable collecting the device data;

    You can either add a device to a device group by.


    The Junos telemetry interface (JTI) sensors use the system ID parameter of Juniper Networks devices to collect data from the devices. So, if not already configured in Paragon Automation, configure the system ID for the Juniper Networks devices. The system ID should be in the following format: <host_name>:<jti_ip_address> and should have the same value as configured on the device; see Edit Devices for configuring the system ID of a device in Paragon Automation.

Data Summarization and Retention Policy

Paragon Automation uses summarization (rollup) profiles to rollup data so that the data is stored in a smaller disk space and performance of the time-series database (TSDB) is improved. Raw network and device data are grouped together into hourly and daily data by using aggregate functions. For more information on data summarization, see Data Summarization Overview.

By default, the data is retained for the following duration:

  • Daily rollup data is stored for 1000 days.

  • Hourly rollup data is stored for 180 days.

  • Raw data is stored for 14 days.

You can modify the default duration for which the rollup data is retained from the Ingest Settings page Administration > Ingest Settings > Retention Policy.

The network archive task uses the rolled-up data for providing network statistics. Also, statistics are displayed on the topology graphs by fetching long range data from rolled-up measurements based on the rollup-query-cutoff-interval pathfinder setting.

rollup-query-cutoff-interval defines the time period for which raw data or rolled-up data is fetched. If data is queried for a time period less than or equal to the value set in rollup-query-cutoff-interval, raw data is fetched, If data is queried for a time greater than rollup-query-cutoff-interval, hourly rolled-up data is fetched. The default value is set to 7 days; that is, by default, rolled-up data is fetched when queried for data greater than 7 days. For information about setting the rollup-query-cutoff-interval parameter, see Modify Pathfinder Settings From the GUI or Modify Pathfinder Settings From the Pathfinder CLI.