Skylar AI 2.3.0 Release Notes

Version 2.3.0 of Skylar AI provides access to Skylar Advisor and Skylar Analytics, each of which requires a separate license. Skylar Advisor currently requires Skylar Analytics.

This release includes improved scaling, enhanced security, more reliable dashboards and more responsive Advisories, and a number of addressed issues for both Skylar Advisor and Skylar Analytics.

The following table lists the minimum and recommended versions of ScienceLogic software required for Skylar AI and its components:

Product Minimum Version Recommended Version
Skylar One 12.3.2 12.5.8 or later
AP2 8.18.43-81 (Jelly Bean) 8.34.116 (Pancake) or later

If you are upgrading from Skylar AI version 2.2.1 to version 2.3.0, see the detailed information in Upgrading from Skylar AI Version 2.2.1.

Features in Version 2.3.0

This section lists the new features that are included in this release of Skylar AI.

Skylar Settings

  • Introduced rate-limiting and session management features to prevent system latency caused by excessive concurrent requests. Account owners in Skylar AI can view and manage active sessions, including a new provisioning configuration for the maximum number of active sessions on an account. Account owners can log out all active users by from the Users page (Settings > Account Access > Users) in Skylar Settings.

  • Updated the platform Helm charts to support requirements for this release. This includes necessary configuration changes for new components and updated service versions.

Skylar Analytics

  • Added a new Vendors table into the Data Visualizer component of Skylar Analytics, and added vendor-specific data columns to the Assets and AssetSoftware tables. These updates let you leverage vendor information, such as company names and contact details, in Skylar Analytics charts and dashboards.

  • The following Skylar One data is now available for dashboards and charts in the Data Visualization component of Skylar Analytics:

    • Windows service monitors
    • Port monitors

Anomaly Detection and Predictive Alerting

  • Updated the buttons on the Skylar AI page in the Skylar One user interface to clarify the text on the various navigation buttons on this page. Some of the Visit buttons were updated to more descriptive terms like View Predictive Events and View Anomaly Events. Also, the layout of this page was reorganized for better flow.

  • Updated the sls-api-anomaly-alerts service to improve connection resiliency and prevent premature connection terminations and associated 500 errors.

Issues Addressed in Version 2.3.0

This section lists the issues that were addressed in this release.

Skylar Advisor

  • Improved the Skylar Advisor interface to make the conversation metrics area responsive to browser window width. This update prevents the metrics display from overlapping with thread titles on narrower screens. (Jira ID: SKY-3878)

  • Addressed an issue where Skylar Advisor did not appropriately collect data from all instances in an account with multiple instances. This update ensures that Skylar Advisor accurately displays stack-specific eventing and data based on the specific instance. (Jira IDs: SKY-4187)

Skylar Analytics

  • Resolved an issue in Skylar Analytics where multi-tenant environments intermittently returned inconsistent data for different stacks. The fix ensures that queries against "Current" views consistently return data for all tenants as expected. (Case: 00640889) (Jira ID: SKY-3740)

  • Addressed an issue where the "Visualization Variety" sample dashboard in the Data Visualization component of Skylar Analytics was missing chart definitions in Skylar AI version 2.1.x. All charts can now be correctly installed and viewed regardless of the installation order of other dashboard bundles. (Jira ID: SKY-3564)

Anomaly Detection

  • Improved the performance of the Anomaly Detection tab in the Skylar One user interface by adding a new index to the aiml_device_policy table, which resolved resolve gateway timeouts when loading anomaly data. (Case: 00642878) (Jira ID: SKY-3830)

  • Addressed an issue in the optimized prediction query to ensure that anomaly detection alerts are generated as expected. (Jira ID: SKY-3807)

To view the Skylar AI documentation online, see the Skylar AI Product Documentation.

Upgrading Skylar AI

If you are currently running Skylar AI version 2.2.1 and you plan to upgrade to this release, version 2.3.0, you will need to run a reset script for Skylar AI before you deploy version 2.3.0. This script ensures that new events are given proper consideration when forming new Advisories in Skylar Advisor, and the script avoids weighting these events negatively based on prior processing.

You only need to run this script if you are using Skylar Advisor version 2.2.1 and you received events for your Skylar Advisor instance. If your instance had no event traffic on version 2.2.1 or if you are a new customer, you can skip this section. You can also skip this section if you are only using Skylar Analytics, without Skylar Advisor.

Upgrading from Skylar AI Version 2.2.1

Before you deploy Skylar AI version 2.3.0, you or your ScienceLogic contact will need to run the skylar_ai/event_cluster/run_event_table_reset_for_ver2.3.sh script once to reset the relevant tables.

To access and run the reset script:

  1. Before deploying version 2.3.0, add the following values to the global secton in values.yaml:

    skylar-advisor-pipeline-event-cluster:
  enabled: false

skylar-advisor-pipeline-event-adv-gen:
  enabled: false

skylar-advisor-pipeline-event-rule-scan:
  enabled: false

skylar-advisor-pipeline-event-temporal-analysis:
  enabled: false

  2. Deploy the rest of the services. The four services above will stop running.

  3. SSH to any other service that has the skylar-ai repository mounted with python, such as the skylar-advisor-api pod. Any of the api services will work if there are more than one.

  4. Change directories to "/workspace/skylar_ai/skylar_ai/event_cluster/run_event_table_reset_for_ver2.3.sh.

  5. Run the reset script once with your tenant ClickHouse instance name:

    ./run_event_table_reset_for_ver2.3.sh <clickhouse_instance>

    For example:

    ./run_event_table_reset_for_ver2.3.sh it_it_default

  6. Review your output. You should see lines like the following in your output:

    DROP TABLE IF EXISTS it_it_default_ai3.AdvisoryOut
DROP TABLE IF EXISTS it_it_default_ai3.AdvisoryOut_staging
...
...

  7. Return to values.yaml and remove the code block you added in step 1.

  8. Redeploy all the services again.

Additional Updates from Skylar AI 2.2.1

The following changes from version 2.2.1 were made in Skylar AI 2.3.0:

  • Centralized the Skylar AI ClickHouse configuration into skylar-clickhouse-chart and upgraded the ClickHouse Helm chart to version 9.1.1. This update includes the deployment of an audit logger with each ClickHouse instance and the addition of Time-to-Live (TTL) settings to all system tables.

  • Also, the shape of the yaml block for the ClickHouse configuration was updated:

    • Skylar AI 2.2.1:

      clickhouse:
 ....

clickhouse-advisor:
 ....

    • Skylar AI 2.3:

      skylar-clickhouse-chart:
  clickhouse:
 ....

clickhouse-advisor:
  clickhouse:
 ....

Known Issues

This section lists the known issues for this release.

Skylar Settings

  • A Skylar AI instance can ingest telemetry from multiple external sources, but only oneSkylar One system should be configured to send telemetry to that Skylar AI instance to prevent data collisions and potential data corruption. To avoid this situation, do not reuse a Skylar AI authentication token with more than one Skylar One systems that are sending data to that Skylar AI instance. (Jira ID: SKY-3538)

  • If the session inactivity timeout value for a Super User or a standard user is adjusted on the Authentication page ( > Account Access > Authentication) of Skylar Settings, the affected user does not get logged out after the new timeout value expires (if that user is currently logged in and remains inactive). (Jira IDs: SKY-3734, SKY-3732)

Skylar Analytics

  • If you had customized tables and views in an older version of the Data Visualization component of Skylar Analytics, that data will not display correctly if you upgrade to Skylar AI version 2.1.0. Any tables and views created in the local database require that the "InstID" and "OrgID" columns contain data for related datasets, charts, and dashboards to be functional. You should not experience this issue if your tables and views in the local database contain values in the "InstID" and "OrgID" columns. (Jira ID: SKY-3824)

  • The "Interface Statistics (Sample)" dashboard was deprecated with Skylar AI version 2.0.0. A Skylar AI administrator will need to remove this dashboard on the Manage Bundles tab of the Dashboards page ( > Analytics > Settings > Dashboard Mgmt). (Jira ID: SKY-2822)

  • If an Admin user removes the "Event Trends (Sample)" dashboard on the Manage Bundles tab of the Dashboards page, the dashboard still appears in the Data Visualization component of Skylar Analytics. Also, if the "Interface Explorer (Sample)" dashboard is added using the Dashboards page, that dashboard does not display in Data Visualization. (Jira IDs: SKY-3739, SKY-3737)

  • Skylar AI uses unique PowerPack naming conventions for creating datasets in the Data Visualization component. If you change the name of a PowerPack, Skylar AI triggers a new dataset, which will cause charts to fail and lose the historical data for that PowerPack. At this time, ScienceLogic recommends that you do not rename any PowerPacks in Skylar One if that Skylar One system is connected to a Skylar AI environment.