Paragon Insights Getting Started Guide
Ready. Set. Let’s go!
Use this guide to get started with Paragon Insights (formerly HealthBot) and start monitoring the health of your network devices.
Learn About Paragon Insights
To learn about how Paragon Insights works, see the Paragon Insights Overview.
The general workflow to get Paragon Insights up and running is as follows:
Part 1: Verify installation and initial setup
Before we get started in the Paragon Insights GUI, you must have:
- Paragon Insights installed. See the Installation Guide for more details.
- Network devices properly setup to stream telemetry data to the Paragon Insights server. See Network Device Requirements for more details on OS and configuration requirements.
Part 2: Onboard Devices and Include in Groups
Log in to the Paragon Insights GUI
- Open a browser (Chrome, Firefox, or Safari) and go to https://<machine-IP>:8080.
- In the login pop-up window:
If this is your first time logging in to Paragon Insights, enter the default username and password: admin and Admin123!.
You are required to change the default password for the admin user. The password change window provides suggestions for password complexity and a strength meter to help you judge the strength of your new password.
Starting from Paragon Insights Release 4.1.0, username is case insensitive.
If you have already changed your admin password, use the new password for this and all future logins.
- Click Save
- On successful log in, you see the Dashboard page.
The dashboard has a Launchpad icon (rocket icon) at the top right corner. The drop-down menu from the icon displays links to the Sizing Tool and the Github repository for Paragon Insights rules called Playbooks (github).
Starting from Paragon Insights Release 4.1.0, the Favorites option, denoted by a star button at top right corner of all pages, allows you to bookmark pages under the Favorites section for easier access.
Discover a Device
- On the left navigation bar, select Configuration > Device.
- Click the + button on the upper right part of the page.
- In the Add Device(s) window that appears, fill in the fields highlighted in red. For the Authentication section, choose the appropriate authentication type and fill in the required information. You can leave the other settings un-configured.
- Click Save & Deploy. A confirmation window replaces the add device window.
- Click Ok
- You should now see the device added to the Device List.
- (Optional) Repeat the steps above and add more devices.
Add the Device to a Device Group
- On the left navigation bar, click on Configuration > Device Group.
- Click on the + button to add a new device group.
- In the pop-up window that appears, fill in the following (highlighted in red) fields. You can leave the other settings un-configured:
- Click Save & Deploy. A confirmation window replaces the add device group window.
- Click Ok
- You should now see the group added to the Dashboard page.
- (Optional) Repeat the steps above to create more groups.
Part 3: Start collecting telemetry data
Review Playbooks and Rules
- In the left navigation bar, select the Configuration > Playbooks page.
- Review the list of predefined playbooks and click on any that look interesting. As you review the playbook details, make a note of any rules that look interesting.
- In the left navigation bar, select the Configuration > Rules page.
- Find one of the rules you noted above and click it. Review
the details and parameters that make up the rule. The goal here is
simply to get a first look at the components and parameters that make
up a rule.
You can see that the chassis.fan/check-fan-health rule is an iAgent rule and uses the ChasissEnvTable from the
- Return to the Configuration > Playbooks page. Let’s instantiate some common predefined playbooks to get started.
- Look to the bottom of the page and click Next to see the remaining available playbooks on page 2.
- Click the Apply icon (the ‘airplane’ icon) for the system-kpis-playbook.
- In the Run Playbook: pop-up window that appears:
Give the playbook an instance name.
In the Device Group drop-down menu, select the device group you created earlier.
- Click Run Instance.
- On the Playbooks page, click the caret beside the system-kpis-playbook. In the drop-down you should see your playbook instance instantiated and running. Note that it may take a few moments.
- Now click Previous to go back to the first page, and repeat the steps above to instantiate an instance of the interface-kpis-playbook.
Part 4: Monitor devices
Monitor Device Health
- In the left navigation bar, select the Dashboard page.
- The carousel across the top of the page shows multiple
widget icons. A carousel is a scrollable group of widgets. A carousel
allows users to drag and drop widgets in any order to customize their
You can double click any of these icons to activate the widget in the lower part of the page. Scroll the carousel left or right to find the Device Group List, Devices List, and the Device Health icons. Double click each of these to activate them in the Dashboard.
- In the left navigation bar select Monitor > Health.
- Click Device Group, and select your device group from the blue pull-down menu.
- In the Devices field, select your device.
- You should now see information being displayed about the device. This page shows the rules in action. The Tile View shows status information grouped by topic area. For example, the system.cpu tile shows CPU status information, with each colored block representing an aspect of the CPU’s status.
- Hover your mouse over the system.cpu tile blocks and review the information.
- Now click the system.cpu heading. Notice that the Table View at right is reduced to show just the system.cpu entries.
- To monitor events over time, click Timeline View at the upper-left of the screen (under the device name). This view shows real-time and past occurrences of events flagged with the health status of minor (yellow) or major (red). Hover your mouse over a colored line or dot and review the information.
You now have Paragon Insights up and running! Feel free to continue exploring the GUI further as you wish.