Known Issues

Upgrade from Release 2.X to Release 4.X

If you are on a 2.X release of Paragon Insights and want to move to Release 3.X or Release 4.X with a multinode (Kubernetes) installation, you must do a fresh installation. To migrate your data from Paragon Insights Release 2.X (Docker Compose) to Release 3.X (Kubernetes) or Release 4.X (Kubernetes) follow the procedure here: Migration from Paragon Insights Release 2.X to 3.X. This issue does not apply if you are upgrading from Release 3.X to Release 4.X.

Upgrade from Release 3.2 (Docker Compose) to Release 4.X

You cannot use the existing setup if you upgrade from Release 3.2 (Docker Compose) to Release 4.X. We recommend that you do not upgrade from Release 3.2 (Docker Compose) to Release 4.X.

User Credentials from Older Releases

Any user credentials present prior to upgrade from 3.X must be re-created after upgrade from release 3.X to Release 4.X. This issue does not apply if upgrading from Release 4.0.0 to or Release 4.1.0.

Paragon Insights CLI

No documentation support is provided for the Paragon Insights CLI. Contact a Juniper Networks representative for support.

Deploy Playbooks

If you deploy playbook instances back-to-back, the deployment may fail due to a database error. This is a rare scenario. You can redeploy or roll back the configuration as this is a timing issue.

GUI for Sensor Precedence and Multiple Active Sensors

Currently, there is no GUI for the sensor precedence and multiple active sensors features. You cannot use the GUI rule editor to write or edit the rules using these features. You can write rules in the .rule file and upload the file to Paragon Insights.

Dashboard Configuration Settings

After you upgrade from Paragon Insights Release 3.X to release 4.1.0, the dashboard configurations that you have saved in the earlier versions of Paragon Insights are not available. This problem doesn’t exist for users upgrading from 4.0.0.

TSDB Ports

The TSDB port is exposed by default in Paragon Insights. If you need to shut down the TSDB port for security reasons, you can use the healthbot tsdb stop-services command. External API queries to TSDB do not need the TSDB port to be exposed. However, if you use external tools such as Grafana, or you need to run a query to the TSDB directly (and not through APIs), the TSDB port must be exposed.