Paragon Insights Frequently Asked Questions

For a complete list of hardware and software requirements, see Paragon Insights Installation Requirements.

A scaling tool, located at https://apps.juniper.net/hb-sizing/, is also available and provides more information on server configurations for a given use case.

The router and switch hardware requirements depend on the rules you are using. For example, if your rules are based on JTI sensors, then check the platform and release requirements on the gRPC support for the Junos Telemetry Interface page.

The router and switch software requirements depend on the data collection methods you are using. For a complete list of software requirements, see the Paragon Insights Installation Requirements.

Paragon Insights provides several benefits, such as automated root cause analysis, greater network visibility, and open integration. For more information about how to use Paragon Insights and its benefits, see the Paragon Insights Overview.

Paragon Insights integrates with various data collection methods, including Junos Telemetry Interface, NETCONF, and SNMP, to provide large volumes of time-sensitive telemetry data. For more information, see the Paragon Insights Overview.

Paragon Insights uses rules and playbooks to extract the needed telemetry data from deployed network devices running Junos OS. A rule is a package of components, or blocks, needed to extract specific information from the network or from a device running Junos OS. Playbooks are the Paragon Insights element that are applied, or run, on your device groups or network groups. For detailed information, see Paragon Insights Concepts.

AppFormix gives you a wide view across domains, whereas HealthBot provides a deep view of the network. They are completely complementary.

AppFormix enables operators to control and visualize how infrastructure resources are utilized by workloads, and plan adequate capacity to ensure application performance. Using AppFormix, operators of software-defined data centers have a toolset for visibility into operational performance and infrastructure resources.

Paragon Insights is a highly automated and programmable device-level diagnostics and network analytics tool that provides consistent and coherent operational intelligence across network deployments. Integrated with multiple data collection methods, Paragon Insights aggregates and correlates large volumes of time-sensitive telemetry data, providing a multidimensional and predictive view of the network.

Open a browser and go to https://machine-IP:8080, where machine-IP is the virtual IP address you entered, to connect to Healthbot services, during installation.

A dedicated service, healthbot_hbmon, monitors the state of the Paragon Insights container and triggers an alarm at predefined settings. Alarms can be viewed in the Paragon Insights Web UI.

For more information, see Checking Paragon Insights Service Status.

Use the healthbot status command to view all services and their status. For example:

$ healthbot status
Name of service               Status
---------------------------------------------
alerta                        Up
api_server                    Up
debugger                      Up
gateway                       Up
grafana                       Up
hb_proxy_syslog               Up
hbmon                         Up
influxdb_db                   Up
iam			              Up
license_client                Up
mgd                           Up
postgres                      Up
redis                         Up
reports                       Up
tsdb_shim                     Up

Use the healthbot version command. For example:

$ healthbot version
HealthBot 4.0.0

Use the healthbot password-reset -u <user-name> [-p password] command. This procedure can be done while Paragon Insights is running. For example:

$ sudo healthbot password-reset -u admin
👨‍💻 New password:
👨‍💻 Confirm password:
✅ Password for user with username: admin has been changed successfully

Yes, before configuring sensor precedence, users must configure devices to retrieve vendor name, operating system, product, platform (product family in a series), and release/version details.