Resolved Issues

The following is a list of resolved issues in HealthBot Release 3.0.1:

• The OS validation for RedHat-based installations would fail due to a mismatch between reported OS distribution and the expected value. This issue has been resolved.

• Removed a restriction on the number of trigger terms that can be used in a rule.

• Previously, the command request healthbot logs device-group healthbot would fail. This issue has been resolved.

• Previously, if you tried to log in to the HealthBot GUI and the server’s time was significantly out of sync, the attempt would fail without any error message. This issue has been resolved by providing an error message at the login window that directs you to check the server’s time synchronization.

  

• Previously, dynamic arguments would fail if the device name contained a dot. This issue has been resolved.

• Previously, when you chose to export data from the Configure > Device, Configure > Device-Group, or Configure > Network pages, HealthBot would only export the data shown on the current page, regardless of whether there was more data available. This issue has been resolved.

• Previously, if you created an instance of the network playbook vpn-view, the device name pull-down menu would not always populate. This issue has been resolved.

• During the initial apt-get install (Debian) or rpm -i (CentOS or RedHat) phase of the installation, if any dependent packages failed to install, the failure was ignored and the installation proceeded despite the errors. This issue has been resolved. Starting with release 3.0.1, a failure to install any of the dependent packages during the initial phase of installation causes the installation to terminate with an error displayed.

• In multinode (Kubernetes) installations, debug jobs failed with error code 500. This issue has been resolved. Debug jobs (Administration > Debug) now succeed.

• Issues regarding rule search:

  • An error was displayed if a rule search was conducted for any rule based on sensor type, for example syslog, if HealthBot also contained a rule that used a custom plug-in BYOI (bring your own ingest) sensor. This issue has been resolved.

  • The rule search pull-down menu did not contain the sensor type BYOI. This issue has been resolved.

  • SNMP rules were not filtered based on ingest-type and SNMP. This issue has been resolved.