Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


New and Changed Features


We’re pleased to announce Paragon Insights Release 4.1.0. In this section, learn about new and changed features in Paragon Insights Release 4.1.0.

Support for Scheduling User-Defined Actions

Paragon Insights Release 4.1.0 supports scheduling user-defined actions (UDAs) and notifications on the Trigger Action page. You can schedule one Trigger Action scheduler in each instance of Paragon Insights. The scheduler runs the UDAs and notifications only for the time interval set in the UDA scheduler.

[See Modify the UDA and UDF Engines.]

Support for iAgent Port Ingest Configuration for Outbound SSH Connections

Paragon Insights Release 4.1.0 supports the iAgent (NETCONF) port at the ingest level for outbound SSH traffic for all device groups. If you configure ports for outbound SSH in device group configurations and ingest, then device group settings take precedence.

[See Paragon Insights Pull-Model Ingest Methods.]

Support for the Server Monitoring Ingest

Paragon Insights Release 4.1.0 supports Server Monitoring sensor to collect server and host data using the third-party plug-in Node Exporter. The Node Exporter plug-in is pre-installed in all server clusters of Paragon Insights. The ingest collects data from servers and hosts to track metrics of CPU, memory, network, traffic, disk, and filesystem and writes the output to a time series database.

[See Paragon Insights Pull-Model Ingest Methods.]

Support for PIN-Standard License

From Paragon Insights Release 4.1.0 onward, the Paragon Insights Standard license, PIN-Standard, replaces the HealthBot’s free-tier license that was available up until HealthBot Release 3.2.0 and Paragon Insights releases 4.0.0. You need a valid license (trial or commercial) to use Paragon Insights and its features. You can add the license before or after upgrading to release 4.1.0 from earlier releases.

With this PIN-Standard license, you can use Paragon Insights to collect telemetry data, and use default or custom playbooks without any advanced features. You can also publish telemetry data externally by using Kafka and Advanced Message Queuing Protocol (AMQP) Publish.

[See Paragon Insights Licensing Overview.]

Use the Grafana UI to Create Graphs and Visuals

Starting in Paragon Insights Release 4.1.0, you can use the Grafana UI to monitor the status and health of your network devices. The Grafana UI renders data from the Paragon Insights time series database (TSDB). You can view this data in the form of charts, graphs, histograms, and heat maps. The Grafana UI is an open-source visualization tool, and you can access it by selecting Monitor > Graphs > Grafana from the Paragon Insights UI.

[See Grafana Overview.]

View and Manage Audit Logs

An audit log is a record of activities that have affected a specific operation or procedure. Audit logs contain information about tasks initiated by using the Paragon Insights GUI or APIs. With Paragon Insights Release 4.1.0, you can view and manage audit logs from the Monitor>Audit Logs page of the Paragon Insights UI.

[See Manage Audit Logs.]

Export Audit Logs in PDF and CSV Formats

Starting in Paragon Insights Release 4.1.0, you can export audit logs in a portable document format (PDF) file and a comma-separated values (CSV) file.

[See Manage Audit Logs.]

Database Name Format

The database name format in TSDB data is changed. In releases earlier than Release 4.1.0, database names were in the “device-group:device-id” format for device groups and “__network:network-group-name” format for network groups. In Release 4.1.0, all database names are prefixed with “hb-default:”. The new name formats are “hb-default:device-group:device-id” for device groups and “hb-default:__network:network-group-name” for network groups. If you access TSDB data directly in the UDA, user-defined function, or custom scripts, ensure that you edit the database name formats.

Configure and Monitor Action Workflows (Beta)

Paragon Insights Release 4.1.0 supports action-workflow monitoring (Beta). An action workflow is an action engine that you can use to configure a set of tasks. In earlier releases, you can configure user-defined actions (tasks), but you cannot monitor or restart a failed action. With this release, you can configure new action workflows, monitor existing action workflows, and manage multiple action-workflow instances in the Paragon Insights UI.

[See Understanding Action Workflows.]