Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Contrail HealthBot Frequently Asked Questions


This topic includes our most frequently asked questions on HealthBot. To learn more about the product, see our Contrail HealthBot User Guide.

What are the hardware and software requirements to install and run HealthBot?

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

A scaling tool, located at, is also available and provides more information on server configurations for a given use case.

What are the hardware requirements for the network devices, such as routers and switches?

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.

What are the software requirements for the network devices, such as routers and switches?

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

What are the benefits of HealthBot?

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

What types of telemetry can HealthBot collect?

HealthBot 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 HealthBot Overview.

What are rules and playbooks?

HealthBot 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 HealthBot element that are applied, or run, on your device groups or network groups. For detailed information, see HealthBot Concepts.

What is the difference between HealthBot and AppFormix?

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.

HealthBot 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, HealthBot aggregates and correlates large volumes of time-sensitive telemetry data, providing a multidimensional and predictive view of the network.

How do I access the HealthBot Web UI?

Open a browser and go to https://<machine-IP>:8080.

How do I monitor the status of the HealthBot application or container?

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

For more information, see Checking HealthBot Service Status.

How do I verify all HealthBot components are running?

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

How can I check which version of HealthBot is running?

Use the healthbot version command. For example:

How can I change or recover the current Healthbot username or password?

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