Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configure Multiple Sensors per Device

Sp-admins or users with create access privilege must note the following guidelines when configuring multiple sensors:

  • When adding multiple sensors to rules, you must ensure that there are no overlapping data or keysets received from the sensors applied to a device. Overlapping keysets can result in duplicate data points, overwriting of data points, and inaccurate evaluation of data. To avoid this, you can use filter expressions such as the where statement in Fields.

  • When you add multiple sensors in a rule in Paragon Insights GUI, you must set a common value for all sensors in the following fields:

    • Frequency field in Sensors tab (sensor frequency)

    • Field aggregation time-range field in Rules page.

    • Frequency field in Triggers tab.

    • Time range field used in triggers, formula, and reference.

    For example, when multiple sensors are added in a rule, all sensors applied to a device must have the same value for sensor frequency, irrespective of the type of sensors. If a rule has iAgent and OpenConfig sensors, the Frequency value in both sensors must be the same. This holds true for all the fields listed above.


    We recommend you use offset values if you cannot match the time range values on different sensors. For more information, see Frequency Profiles and Offset Time.

    However, the frequency you set in a frequency profile will override the frequency values set in multiple sensors in a rule.

  • A Rule with multiple sensors is applied on all devices added in a particular device group. It is assumed that the devices in a device group support the types of sensors used in Paragon Insights rules.

    Sometimes, not all devices in a device group can support the same type of sensor. For example, the device group DG1 has an MX2020 router with OpenConfig package installed and another MX2020 router configured without the OpenConfig package. The first MX2020 router would support OpenConfig sensor whereas, the second MX2020 router would not support the same sensor.

    To avoid such scenarios, you must ensure that all devices in the same device group support the types of sensors used to collect information.

To add multiple sensors in a rule:

  1. Navigate to Configuration > Rules > Add Rule.

    Rules page appears.

  2. Enter the Paragon Insights topic and rule name, rule description, synopsis, and optionally, the field aggregation time-range and rule frequency. For more information on these fields in Rules page, see Paragon Insights Rules and Playbooks.
  3. Click Add Sensor button in Sensors tab and fill in the necessary details based on the type of sensor you choose.

    Repeat step 3 to add as many sensors as you need for your use case.

  4. Configure fields for the sensors in the Fields tab.
  5. Configure sensors in Rule Properties tab to set multiple sensors active.

    You must enter all the sensors, earlier configured in the rule, under the supported-devices hierarchy in Rule Properties. For example, if you configured sensors s1, s2, and s3 in a rule, the Rule Properties configuration must also include the same sensors:

    You can also write a new rule and upload it to the Paragon Insights GUI.

    The rule must follow the curly brackets format ( { ) and indentation for hierarchical structure. Terminating or leaf statements in the configuration hierarchy are displayed with a trailing semicolon (;) to define configuration details, such as supported version, sensors, and other configuration statements.

  6. Click Save & Deploy to apply the new sensors in your network or click Save to save the configurations of the new sensors and deploy them later.