New and Changed Features
We’re pleased to announce the general availability of HealthBot Release 2.0.0. With this release, HealthBot now delivers:
To provide greater flexibility and an easier-to-use interface, the Plots page was replaced by the Graph page. The Graph page allows you to create detailed graphical information from the device health data collected by HealthBot. Graph types include time series graphs, histograms, and heatmaps. You can create, save, and view multiple graphs of the same or different type on a single canvas.
Multivendor and Multi-OS Support
In addition to devices running Junos OS, you can now add devices running Junos OS Evolved and Cisco IOS XR to HealthBot.
Kafka Publish for Notifications
In addition to the Slack and Webhook notification delivery methods, HealthBot now provides an option to publish notifications to a Kafka cluster.
LFA Streaming Syslog
In addition to automatic Kafka feeds, you can now create automatic syslog feeds to send log messages from devices to the HealthBot log file analysis (LFA) application.
When creating a HealthBot rule for a network group, you can use a new formula named Outlier Detection. This feature can detect and alert you when a device's behavior deviates from the behavior of a group of devices. HealthBot Release 2.0.0 supports DBSCAN and kfold-3-sigma algorithms for the outlier detection formula.
When creating a HealthBot rule for an iAgent sensor, you can now choose the YAML-based table from a drop-down list after you select the YAML file. You’re also given the option to specify a target or dynamic arguments that are required by the table you’ve selected.
When creating a HealthBot rule, you can now specify metadata for the rule, such as hardware dependencies, software dependencies, and version history. This data can be used for informational purposes or to verify whether or not a device is compatible with a HealthBot rule.
You can now pause a running playbook instance. When an instance is paused, data collected prior to pausing the instance is retained in the system, but no new data is collected or analyzed until the instance is resumed.