SL1 AP2 Gelato version 8.14.26 Release Notes

The Gelato release for AP2 version 8.14.26 includes the new Skylar AI landing page, improved data visibility and management for dashboard widgets, the ability to access the Device Dashboards page in the classic SL1 user interface, assorted changes to the Service Investigator page, and a new Relationships and Memberships panel in the Device Investigator that provides details about related devices and services.

AP2 releases are separate from SL1 platform releases to provide updates and improvements more frequently.

This release includes the following new features and enhancements:

Introduction to the Skylar AI landing page
A new Skylar Analytics Summary widget on the Events Details page
Enhancements to the Service Investigator page user interface
Improved data visibility and management for Dashboard widgets
A new Relationships panel in the Device Investigator that displays details about related devices and services
Plus several additional new features and enhancements

These release notes provide a comprehensive list of the features, enhancements, and addressed issues that are included in this release.

Before You Install or Upgrade

Before you install or upgrade to AP2 Gelato, ensure you are running one of the following SL1 versions:

12.1.2 (Oracle Linux 8 instances only)
12.2.0
12.2.1.2

You do not need to download or install AP2 Gelato if you are on SL1 version 12.3.0 or above, as it is included by default.

For details on upgrading SL1, see the appropriate SL1 platform release notes.

This update is available to both on-premises and cloud-based (SaaS) SL1 systems. The AP2 Gelato update must be administered to systems that host AP2. All SL1 appliances in your stack must be on the same AP2 version.

Installing or Uninstalling AP2 Gelato

To install AP2 Gelato version 8.14.26 on to your system, you will need to download and install both the libem7 and AP2 Gelato RPM files from the ScienceLogic Support site.

You do not need to download or install AP2 Gelato if you are on SL1 version 12.3.0 or above, as it is included by default.

To install AP2 Gelato version 8.14.26:

If you have not already done so, install or upgrade your SL1 system to either the 12.1.2 Oracle Linux 8 (OL8) release, 12.2.0, or 12.2.1.2. For more information, about upgrading to those releases, see the appropriate SL1 platform release notes.
- If you are installing AP2 Gelato version 8.14.26 on SL1 versions 12.2.0 or 12.2.1.2, skip to step 8.
- If you have already downloaded and installed the latest libem7 RPM file from the ScienceLogic Support site, skip to step 8.
- If you have downloaded the latest libem7 RPM file from the ScienceLogic Support site, but have not yet installed the file, skip to step 6.
- If you are installing AP2 Gelato version 8.14.26 on SL1 version 12.1.2, proceed to step 2.
- If you are unsure where you stand in the download and installation process, proceed to step 2.
Either go to the console of the SL1 Database Server or use SSH to access the Database Server. Check to see if you already have the libem7 RPM file downloaded or installed by running the command sudo rpm -q libem7-ipcserver. The correct version should appear as libem7-ipcserver-0.2.0-2.el8.x86_64.rpm.
- If you do not see the correct version, proceed to step 3.
- If you see the correct version, skip to step 5.
Download the libem7 RPM file locally to your machine from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBt4z000000GsHACA0/libem7
Either go to the console of the SL1 Database Server or use SSH to access the Database Server.
- For AWS Systems: At the shell prompt, copy the RPM file to your SL1 system by running the following command:
- For On-premises systems: At the shell prompt, copy the RPM file to your SL1 system by running the following command:
If you have the correct version installed, verify if the libem7 is running properly by running the following command: sudo systemctl status libem7.
- If the status of the libem7 RPM file displays active in the Active field, skip to step 8.
- If you have downloaded the libem7 RPM file, but it is not showing as active, the libem7 RPM file has not yet been installed on your device. Proceed to step 6 to install the RPM file.
Once you have downloaded the correct libem7 RPM file, install the file on your device by running the following commands at the shell prompt:

sudo dnf install -y libem7-ipcserver-0.2.0-2.el8.x86_64.rpm --disablerepo=*

sudo systemctl enable --now libem7.socket

sudo systemctl enable --now libem7.service

sudo systemctl restart libem7.socket

sudo systemctl restart libem7

sudo systemctl status libem7

Verify the status of the libem7 RPM file displays active in the Active field by running the following command:

sudo systemctl status libem7

Download the AP2 Gelato RPM file locally from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL0000000Q490AE/gelato
Either go to the console of the SL1 Database Server or use SSH to access the Database Server.
- For AWS Systems: At the shell prompt, copy the RPM file to your SL1 system by running the following command:
- For On-premises systems: At the shell prompt, copy the RPM file to your SL1 system by running the following command:
Install the AP2 RPM file on the Database Servers and the Administration Portal by running the following command on those systems:

sudo dnf upgrade -y nextui-<gelato-release-ap2-version>.rpm --disablerepo=*

where <gelato-release-ap2-version> is the AP2 Gelato release version.

Enter y to confirm the installation of the AP2 RPM file.
Reload the daemon service by running the following command:

sudo systemctl daemon-reload

Restart the NextUI service by running the following command:

sudo systemctl restart nextui.service

AP2 will be inaccessible for a few minutes after restarting the NextUI service.

To uninstall the Gelato release features for AP2 version 8.14.26:

Whether you are currently on 12.1.1, 12.1.2, 12.2.0, 12.2.1, or 12.2.1.2, if you have previously installed AP2 Biscotti, Croissant, Doughnut, Espresso, or French Toast, download the rollback RPM file by considering the table below:

AP2 Releases	Compatible SL1 Releases	RPM File Links
8.7.96 (French Toast)	12.1.2, 12.2.0, 12.2.1	https://support.sciencelogic.com/s/release-file/aBtVL0000000IzR0AU/frenchtoast
8.7.37 (Espresso)	12.1.1, 12.2.0, 12.2.1	https://support.sciencelogic.com/s/release-file/aBtVL0000000C1B0AU/espresso
8.6.30 (Doughnut)	12.1.1, 12.2.0, 12.2.1	https://support.sciencelogic.com/s/release-file/aBtVL00000008nB0AQ/doughnut
8.5.70 (Croissant)	12.1.1, 12.2.0	https://support.sciencelogic.com/s/release-file/aBtVL00000002530AA/croissant
8.0.20 (Biscotti)	12.1.1, 12.2.0	https://support.sciencelogic.com/s/release-file/aBt4z000000GsH0CAK/biscotti

If you have not installed any AP2 releases, download the AP2 RPM files from either AWS or the ScienceLogic Support site:

For SL1 12.1.2: https://support.sciencelogic.com/s/release-file/aBtVL0000000KZp0AM/ap21212
For SL1 12.2.0: https://support.sciencelogic.com/s/release-file/aBt4z000000GsH0CAK/biscotti
For SL1 12.2.1.2: https://support.sciencelogic.com/s/release-file/aBtVL00000008nB0AQ/doughnut

You can only roll back to an AP2 version that you have previously installed.

Once you have the AP2 RPM files downloaded locally, either go to the console of the SL1 Database Server or use SSH to access the Database Server.
- For AWS Systems: At the shell prompt, copy the RPM file to your SL1 system by running the following command:
- For On-premises systems: At the shell prompt, copy the RPM file to your SL1 system by running the following command:
Install the RPM file on your device by running the following command:

sudo rpm -U --force --replacefiles nextui-<rollback-ap2-version>.rpm

where <rollback-ap2-version> is the rollback AP2 version.

After the installation is complete, run the following commands to reload the daemon service:

sudo systemctl disable libem7.socket

sudo systemctl stop libem7

sudo systemctl deamon-reload

Restart the NextUI service by running the following command:

sudo systemctl restart nextui.service

Important Upgrade Notes for AP2 Gelato 8.14.26

Global Manager Deployment

When deploying or upgrading Global Manager systems, the Global Manager stack and all of its child stacks must run on the same SL1 build version, as well as the same versions of AP2 and Oracle Linux.

New Features and Enhancements in AP2 Gelato version 8.14.26

This section describes the features and enhancements that are included in SL1 AP2 Gelato version 8.14.26.

Anomaly Detection

What's new: Introduction to the new Skylar AI and Anomaly Detection pages. The Machine Learning page has been renamed to Skylar AI. This page lets you directly access key Skylar AI components. You can access the Skylar AI page from the main navigation menu, or from the Advanced Menu page.

The following updates were made to support this enhancement:
- The Machine Learning page has been renamed to Anomaly Detection, and the Machine Learning Thresholds page has been renamed to Anomaly Detection Thresholds. These pages and all of their content are accessible from the new Skylar AI page.
- The Anomaly Detection page (formerly the Machine Learning page) now lists every Dynamic Application metric with its Anomaly Detection status, even metrics that will not alert when the anomaly score exceeds a threshold.
- For an SL1 system that is connected to a Skylar Automated RCA system, the Anomaly Detection column was removed from the Anomaly Detection page, as this column is no longer relevant with this release. Any devices listed on the Anomaly Detection page have anomaly detection enabled by default. This column was also removed from the Device Investigator, Event Investigator, and Service Investigator pages that contain anomaly detection data.

Additional Anomaly Detection Updates

The Skylar AI logo in the main navigation menu now adjusts its color based on the theme you are currently on (light vs dark).
The URLs in SL1 for the Anomaly Detection and Anomaly Detection Thresholds pages were updated from /aiml to the following structure: /skylar-ai/anomaly-detection and /skylar-ai/anomaly-detection/thresholds.

Business Services

What's new: Enhancements to the Service Investigator and Business Services pages. The Business Services and Service Investigator pages have been updated to include new features such as new information in the Timeline panel on the Service Investigator page.

The following updates were made to support this enhancement:
- Updated the Zebrium icon to the Skylar icon in the Timeline panel of the Service Investigator page.
- The Last Edited field in the Overview panel at the top of the Service Investigator page now displays the date the service was last edited.
- Added a Refresh Interval column field to the services inventory table on the Business Services page. To add this column, click the gear icon at the top of the inventory table, select Column Preferences from the drop-down menu that appears, then select Refresh Interval.
What's new: Improved Service Policies page. The Policies page has been renamed to the Service Policies page and includes new information and features.

To support this enhancement, the following columns were added to the Service Policies page:
- Status: The status of the service policy. This field indicates if the service policy you have selected is "Valid" or "Invalid". Moving your cursor over the "Invalid" text in the Status column field will display a mouse-over text that previews the reason for its invalid state and the rule number associated with it.
- Service Count: The number of services assigned to the policy. Moving your cursor over the number that displays under the Service Count column will display a mouse-over text that shows all of the services aligned to that service policy.
- Date Edited: The date the service policy was last edited.
- Last Edited By: The user to last edit the service policy.

For more information: See the section on Using the Service Investigator in the Business Services manual.

Additional Business Services Updates

Updated the status policies for "Aggregate," "Business," and "IT" services and their corresponding rules for calculating health, availability, and risk values.
You can now enable or disable services in bulk on the Business Services page.
The onDemand process currently retrieves data by calculating the "lastValue" in the last three intervals. If the value of the two most recent intervals is null, the system will log the calculation as incomplete because metrics did not exist during that time.

Dashboards

What's new: Improved data visibility and management for Dashboard widgets. The widgets on the Dashboards page can now display different scale prefix options for non-percentage-based metrics. You can select one of these scale prefixes, such as Kilo, Mega, Giga, Tera, and so on, if you want dashboards to auto-scale the visualization of metrics that have the same metric unit prefix.

The following updates were made to support this enhancement:
- The widgets that use the following visualizations allow you to select different scale prefix options for non-percentage-based metrics:
- The Select Visualization drop-down list on the Create Widget page now lists the available visualization options in alphabetical order

Devices

What's new: Added a new Relationships and Memberships panel to the Device Investigator.The new panel in the Device Investigator displays details about the other devices and services that have relationships to the selected device.

The following updates were made to support this enhancement:
- The Relationships and Memberships panel, which appears in the Device Investigator by default.
- Added a "deviceGroup" search parameter to the "relatedNodes" query in GraphQL to support the Relationships panel in the Device Investigator.

For more information: See the section on Using the Device Investigator in the Managing Devices manual.

Additional Devices Updates

Updated the method for performing bulk actions to multiple devices on the Devices page. Previously, you could select from several action-specific icons at the top of the page. With this update, those icons have been replaced by an Actions drop-down menu that includes a list of available bulk actions. With this update:
- You can now change the collector group assigned to one or more devices from the Devices page. On the Devices page, click the checkboxes of the devices you want to update and then click Actions > Change Collector Group. Select a new collector group from the list, and then click Change to confirm your selection.
- You can now enable or disable data collection on one or more devices from the Devices page. On the Devices page, click the checkboxes of the devices you want to update and then click Actions > Change Collection State. Use the toggle to either enable or disable collection, and then click Save to confirm your selection.
In the Basic Menu and Advanced Menu, the Device Manager option was relabeled to Classic Devices.

Events

What's new: New Skylar Analytics Summary panel.Added a new Skylar Analytics Summary panel to the Events Details page for predictive alerts from Skylar AI. This panel displays a graphic from Skylar AI-sourced predictive alert corresponding with the event ID.

The following updates were made to support this enhancement:
- You can now filter your search by events sourced by Skylar AI in the following inventory tables on these pages:
- Added Skyler AI to the Event Source drop-down option. You can also filter the events on the Events page by selecting Skylar AI as the Event Type.
- On the Event Policy Editor page, the Skylar AI Severity drop-down for Skylar AI sourced events now defaults to Disregard Severity.

For more information: See the section on Defining and Editing Event Policies in the Events manual.

Additional New Features and Enhancements for Gelato

Devices

When adding devices using the guided discovery process from the Discovery Sessions page (Devices > Discovery Sessions), devices for which your SL1 system does not have the required entities will now appear in a secondary section at the bottom with a new warning note. This note will specify why you cannot add the selected device and the necessary prerequisites.

Global Manager

Changing the name of your global manager stack will retrieve and return the correct version information.

GraphQL

Removed both the enabled and status fields from "aiMachineLearningMetricAnomalies" device queries in GraphQL and added an alerting status. The alerting status will send an alert whenever the anomaly score exceeds a set threshold, and then send an alert that maps to an event of the appropriate severity.
Updated the "deviceMetrics" API by adding new endpoints that enable any monitor-related data to be queried as a new "collectionType" object.
Added the ability to search Dynamic Applications associated with specific presentation IDs by adding "presentationID" as an "IDSearch" variable for the existing "DynamicApplicationSearch" function. This update enables you to search Dynamic Applications by finding the corresponding APIs associated with specific presentation IDs.
Added a new status variable to the GQL API for device groups. This variable represents the device statuses within a device group as a singular unit.

Platform Security

When logging in for the first time with a new SL1 user account, a Notice dialog appears, prompting you to accept an agreement that you may use the product only in accordance with the applicable contract and within the scope of the rights purchased by your organization. To accept, check the box and then click Agree.

User Interface

Throughout SL1, references to "Zebrium" have been changed to "Skylar," including in the following locations:
- On the Events page, in the Event Source drop-down column, the Zebrium option is now Skylar RCA.
- On the Events page, in the Event Type drop-down column, the Zebrium Accepted, Zebrium Suggested, and Zebrium Custom options are now Skylar RCA Accepted, Skylar RCA Suggested, and Skylar RCA Custom.
- On the Device Investigator, text references to "Zebrium" were changed to "Skylar AI".
- On the Events tab of the Device Investigator, the Zebrium Events drop-down option is now Skylar Events.
- On the Event Policy Editor page, all references to "Zebrium" are now "Skylar RCA".
- In the Match Logic tab of the Event Policies page, the Zebrium Accepted, Zebrium Suggested, and Zebrium Custom options under the Zebrium Alert Type drop-down field are now Skylar RCA - Accepted, Skylar RCA - Suggestion, and Skylar RCA - Custom under the Skylar Automated RCA Alert Type drop-down field.
- In the Match Logic tab of the Event Policies page, the Zebrium Severity field is now Skylar Automated RCA Severity.
- On the Events Details page, the Zebrium Root Cause Summary widget has been renamed to Skylar Automated RCA Summary.
- On the Events Details page, the View Full Root Cause Report in Zebrium button has been relabeled as View Details in Skylar Automated RCA.

Throughout SL1, references to "Machine Learning" and "Metric Anomalies" have both been changed to "Anomaly Detection", including the following locations:
- Updated all text references to "Metric Anomalies" to "Anomaly Detection" and "Anomaly Count" on all pages related to Business Services, where relevant.
- On the Device Investigator, text references to Zebrium were changed to Skylar.
- On the Events tab of the Device Investigator, the Zebrium Events drop-down option is now Skylar Events.
- The Machine Learning tab of the Device Investigator is now labeled Anomaly Detection.
- On the Machine Learning tab, the Add ML Metric button has been relabeled to Add Alert Policy.

Issues Addressed in SL1 AP2 Gelato version 8.14.26

This section describes the issues that were addressed in SL1 AP2 Gelato version 8.14.26.

Business Services

Resolved an issue where business service status policies were incorrectly calculating the Health state of services. (Case: 00421078) (Jira ID: SLUI-19584)

Events

Resolved an issue that caused high latency when loading events on the Events page. (Case: 00455708) (Jira ID: SLUI-20411)

Global Manager

Resolved an issue that was causing some Global Manager pages to not load due to child stacks returning an HTTP 502 error, resulting in users having to manually disable monitoring of those child stacks. (Jira ID: SLUI-20184)

Known Issues

The following known issues affect version 8.14.26 of the AP2 Gelato release:

Organizations must have one or more accounts assigned to them to ensure the relevant services are saved. (Jira ID: SLUI-17810)
The Set as Home Page button on the Dashboards page is disabled for newly created dashboards and existing dashboards that were imported. (Jira ID: SLUI-19539)
Services that are added or created to the N-tier hierarchy have their RCA Options field set to Disabled by default. (Jira ID: SLUI-18852)

To work around this issue, edit the service you want to configure by manually updating the RCA Options field to RCA Enabled (contributors only).

For services where the RCA Options field is enabled and a child service has been removed, SL1 will not compute the health, availability, and risk values until the Service Topology Engine returns an updated topology, which occurs every 5 minutes by default. (Jira ID: SLUI-18853)

Before deleting child services in a 3-tier hierarchy, check to see if the parent service has the RCA Options field Enabled, then set this field to Disabled if it is not already.

When editing information about a collector group using the Collector Groups page (Manage > Collector Groups), when you click Save, SL1 might remove information about any Data Collectors aligned to that collector group, even if you did not make any such changes. To work around this issue, you can instead make changes to collector groups using the Collector Group Management page (System > Settings > Collector Groups). (Jira ID: SLUI-19657)
When deleting a device from the Devices page from the Actions menu (), the Delete Devices modal displays for an indefinite period of time. (Jira ID: SLUI-19738)

To work around this issue, select the checkbox next to the device(s) you want to delete, click Delete Devices to open the Delete Devices modal, and then click Delete.

When creating a template from a Business Service, you might receive an error if the number of constituents and maximum constituents are greater than the maximum number of policies, which has a default value of 100. To work around this issue, you must increase the maximum number of policies using a GraphQL mutation, replacing <increased value> with a larger numerical value such as "1000": (Jira ID: SLUI-19654)

mutation updateMaxValue{

updateFeatureToggle(id: "system:BUSINESS_SERVICES_MAX_POLICIES", value: "<increased value>") {

value

}