This section lists the known issues in Paragon Insights Release 4.2.0.
If you are using Paragon Insights Release 2.x and want to upgrade 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 Migration from Paragon Insights Release 2.x to 3.x procedure. This issue does not arise if you are upgrading from Release 3.x 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.
Any user credentials present before upgrade from 3.x must be re-created after upgrade from release 3.x to Release 4.x. This issue does not arise if you are upgrading from Release 4.x.
After you upgrade from Paragon Insights Release 3.x to Release 4.x, 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 Release 4.x.
We don't provide documentation support for the Paragon Insights CLI. Contact a Juniper Networks representative for support.
If you deploy playbook instances back-to-back, the deployment may fail because of a database error. This is a rare scenario. As this is a timing issue, you can redeploy or roll back the configuration.
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.