Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Add a Device Group

You must add a device to one or more device groups before you can apply rules and playbooks to a device.

To add a device group:

  1. Click Configuration > Device Groups.

    The Device Group Configuration page appears.

  2. Click the add (+) icon.

    The Add Device Group page appears.

  3. Configure the device group fields as per Table 1.

    Fields marked with asterisk (*) are mandatory.

  4. Do one of the following:
    • Click Save to save the configuration. Selecting this option does not deploy the new device group configuration.


      You can click the Health Configuration Deployment Status icon on the top-right corner to commit, deploy, or rollback the configuration settings. For more information, see Commit or Roll Back Configuration Changes in Paragon Insights.

      A confirmation message appears stating that the device group is successfully created. The new device group is added to the Device Group page.

    • Click Save and Deploy to save and immediately deploy the device group configuration.

      A confirmation message appears that device group is successfully created and deployed.

Table 1: Fields on Add Device Group Page





Enter a name for the device group.


Enter a description for the device group.


Select one or more devices to add to the device group.


Flow Ingest Deploy Nodes

Select one or more nodes from the existing nodes list to specify which nodes must receive the NetFlow traffic if your installation is a multi-node installation using Kubernetes.

Ingest Frequency Profiles

Select one or more profiles from the list that should override the rules or sensor frequency settings.


Select one or more health report profiles from the list to generate reports for the device group. Reports include alarm statistics, device health data, and device-specific information (such as hardware and software specifications).

Retention Policy

Select a retention policy from the list for time series data used for root cause analysis (RCA) in this device group. By default, the retention policy is 7 days. For more information, see Configure a Retention Policy and Time Series Database (TSDB) Overview.


You can collect logs of different severity level for a device group. Use the following fields to configure which log levels to collect.

Global Setting

Select one of the following levels for log messages that you want to collect for the device group:

  • None—Disables logging functionality

  • Error

  • Debug

  • Warn—Conditions that warrant monitoring

  • Info—Any events or non-error conditions of interest


By default, the logging level is set to Error.

Service Logging Overrides

Select the log level for any of the following services that you want to configure differently from the Global Log Level setting:

  • Open Config

  • iAgent

  • Native GPB

  • Netflow

  • SNMP

  • SNMP Notification

  • Syslog

  • Reports Generation

  • Non-Sensor rules

  • Trigger Evaluation

  • ML Model Builder


The log level that you select here for a specific service takes precedence over the Global Log Level setting.


  • You can use the Notifications feature to organize, track, and manage KPI event alarm notifications received from devices in the device group.

  • To receive alarm notifications for KPI events that have occurred on your devices, you must first configure the notification delivery method for each KPI event severity level (Major, Minor, and Normal).

    Select the delivery method from the respective lists.


Native Ports

(Native GPB sensors only) Enter the port numbers on which the Junos Telemetry Interface (JTI) native protocol buffer connections are established as comma separated values.

Flow Ports

(NetFlow sensors only) Enter the port numbers on which the NetFlow sensor data is received as comma separated values. The port numbers must be unique.

sFlow Ports

(sFlow sensors only) Enter the port numbers on which the sFlow sensor data is received as comma separated values.

The port numbers must be unique.

Syslog Ports

Enter the UDP ports on which syslog messages are received as comma separated values.

SNMP Notification Ports

Enter the SNMP Notification port numbers as comma separated values.

Outbound SSH Ports

Enter TCP port number(s) for NETCONF outbound SSH connections as comma separated values.


To improve the performance and disk space utilization of the time series database, you can configure data summarization methods to summarize the raw data collected.

Use the following fields to configure data summarization:

  • Profiles—Select the data summarization profiles which you want to apply to the ingest data. To edit or view details about saved data summarization profiles, see Summarization Profiles page under the Configuration menu.

  • Time Span—Enter the time span (in minutes) for which you want to group the data points for data summarization.

For more information, see About the Data Summarization Page.

Data Rollup Summarization

Select the rollup summarization policy for the device group.


You can configure the PCE to publish sensor and field data to AMQP/Kafka servers for a specific device group:

  • Notification Groups—Select the notification groups for data publishing.


    Only kafka-publish and amqp-publish are currently supported.

  • Rules—Select the rule topic and rule name pairs that contain the field data you want to publish.

  • Sensor—Select the sensor paths or YAML tables that contain the sensor data you want to publish. No sensor data is published by default.


Select one or more tagging profiles from the existing profiles list. Tagging makes use of profiles to set conditions, define new fields and keys, and insert values into those fields after creation. For more information, see Paragon Insights Tagging Overview.

Root Cause Analysis

Mode is enabled by default. Disable Mode if you do not want the device group to be a part of resource discovery and dependency process.

Exclude Resources field allows you to select device resources that must be excluded from resource and dependency formation.

IFA Deploy Nodes Enter IP address of nodes where In-band Flow Analyzer (IFA) ingest must be deployed in a multinode Paragon Insights installation.
IFA Ports

Enter a UDF port number from 1 to 65535.

The port receives IFA sensor data in Paragon Automation.