SL1 AP2 French Toast version 8.7.96 Release

The French Toast release for AP2 version 8.7.96 includes feature enhancements to the Business Services and Collector Groups pages, such as the ability to convert multiple SL1 Collectors to OL8 in a single bulk action, and the introduction of Skylar AI as an event source on all event policy inventory tables.

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

This release includes the following new features and enhancements:

Several feature updates to the Collector Groups page
Skylar AI as an event source on the Event Policy Editor page
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

Ensure you are running version 12.1.2 Oracle Linux 8 (OL8) before installing AP2 French Toast.

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 running 12.1.2 Oracle Linux (OL8). The AP2 French Toast update must be administered to systems that host AP2. All SL1 systems must be on the same AP2 version.

Installing or Uninstalling AP2 French Toast

You can find all AP2-related files on AP2 Release Versions page of the ScienceLogic Support site (SL1 Product Downloads > SL1 Platform > AP2 Releases).

To install AP2 French Toast version 8.7.96:

If you have not already done so, upgrade your SL1 system to either the 12.1.2 Oracle Linux 8 (OL8) release, 12.2.0 Oracle Linux 8 (OL8) release, or the 12.2.1 Oracle Linux 8 (OL8) release. For more information, about upgrading to those releases, see the appropriate SL1 platform release notes.
- If you are installing AP2 French Toast version 8.7.96 on SL1 versions 12.2.0 or 12.2.1, proceed to step 9.
- If you have already download and installed the libem7 RPM file from the ScienceLogic Support site, proceed to step 9.
- If you have downloaded the libem7 RPM file only, and need to install the file, skip to step 6.
- If you have not downloaded the libem7 RPM file and need to install the file, skip to step 2.
Due to a technical issue with the 12.2.1 patch bundle, the file has been temporarily removed. The 12.2.1 patch bundle will be re-published once the issue has been resolved.
If you are installing AP2 French Toast on SL1 version 12.1.2, verify if the libem7 RPM file is already installed and if it is on the correct version by running the following command:

sudo rpm -q libem7-ipcserver
libem7-ipcserver-0.2.0-2.el8.x86_64

Verify if the libem7 is running properly by running the command sudo systemctl status libem7.
- If the status of the libem7 RPM file displays active in the Active field, skip to step 9.
- If the libem7 RPM file is not active, the libem7 RPM file has not yet been installed on your device. Proceed to step 4.
- If the libem7 RPM file is not active, but you have downloaded the libem7 RPM file, then you will need to install the file on your device. Proceed to step 6.
Download the libem7 RPM file locally to your machine from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL0000000KQ90AM/libem7ipcserver0202
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 libem7 RPM file by running the following command:

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

Enter y to confirm the installation of the libem7 RPM file.
At the shell prompt, run the following commands:

sudo systemctl enable --now libem7.socket

sudo systemctl enable --now libem7.service

sudo systemctl restart libem7.socket

sudo systemctl restart libem7

Download the AP2 French Toast RPM file locally from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL0000000IzR0AU/frenchtoast.
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-<FrenchToast-release-ap2-version>.rpm --disablerepo=*

where FrenchToast-release-ap2-version is the AP2 French Toast release version.

If you are using an SL1 environment where the container database (CDB) does not have internet access, your AP2 French Toast RPM file will not download. You can temporarily bypass this restriction by running the following command:

scp -i <aws-system-pem>.pem -o StrictHostKeyChecking=no nextui-<FrenchToast-release-ap2-version>.rpm em7admin@<system-ip-address>:/home/em7admin/

where aws-system-pem is the PEM file for the AWS system, and FrenchToast-release-ap2-version is the AP2 French Toast release version.

Enter y to confirm the installation of the AP2 RPM file.
After the installation of both RPM files is complete, run the following command to reload the daemon service:

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 confirm that AP2 French Toast version 8.7.96 has been properly installed on your SL1 system, log in to SL1, click your username in the upper right corner of the page, select About from the drop-down field, and then confirm that the ap2 field starts with 8.7.96.

To uninstall the French Toast release features for AP2 version 8.7.96:

Whether you are currently on 12.1.2, 12.2.0, or 12.2.1, if you have previously installed AP2 Biscotti, Croissant, or Espresso before upgrading to 12.1.2 or higher, download the rollback RPM files below:
- If you have already installed AP2 Espresso before upgrading your system to 12.1.2, download the AP2 Espresso RPM file from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL0000000C1B0AU/espresso
- If you have already installed AP2 Doughnut before upgrading your system to 12.1.2, download the AP2 Doughnut RPM file from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL00000008nB0AQ/doughnut
- If you have already installed AP2 Croissant before upgrading your system to 12.1.2, download the AP2 Croissant RPM file from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL00000002530AA/croissant
- If you have already installed AP2 Biscotti before upgrading your system to 12.1.2, download the AP2 Biscotti RPM file from the ScienceLogic Support site: 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: https://support.sciencelogic.com/s/release-file/aBtVL00000008nB0AQ/doughnut
You can only roll back to an AP2 version that you have previously installed.
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 French Toast 8.7.96

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 French Toast version 8.7.96

This section describes the features and enhancements that are included in SL1 AP2 French Toast version 8.7.96.

System Administration

What's new: You can now convert multiple SL1 Collectors to Oracle Linux 8 (OL8) in a single bulk action. Convert SL1 Collectors to OL8 in a single bulk action on the Collector Groups page by selecting the boxes next to the collector groups that contain the SL1 Collectors you want to convert, then clicking the Convert Collectors to OL8 button at the top of the page. The new Select Collectors to Convert to OL8 modal will appear. This modal contains a table that lists all of the collectors from the collector groups you have selected. Check the boxes next to the SL1 Collectors you wish to convert, then click Convert. The table contains the following column fields:

Collector ID: The unique identifier code assigned to the SL1 Collector.
Collector Name: The name of the SL1 Collector.
Status: The status of the SL1 Collector.
Collector Group: The collector group to which the SL1 Collector belongs.
Node type: The node type of the SL1 Collector.
OS Version: The current version of the operating system.

Alternatively, you can convert SL1 Collectors from a single collector group. On the Collector Groups page, click the Actions button () for that particular collector group, and then select Convert to OL8. The Select Collectors to Convert to OL8 modal will appear for that one particular collector group you have selected. You can also filter search column fields by keywords.

What's new: New notification banner on the Collector Groups page. There is a new banner at the top of the Collector Groups page that reads, "Collector groups need to be staged to allow conversion to OL8". This banner will continue to display until all collector groups are staged successfully. You can click the Stage Collector Groups button in the banner to begin staging your collector groups. Upon clicking the Stage Collector Groups button, a confirmation modal will appear. Upon confirmation, SL1 will begin staging your collector groups.

To upgrade your Message Collectors and Data Collectors to Oracle Linux 8 (OL8), you must first upgrade the Database Server or Data Engine to SL1 12.1.2, then upgrade SL1 to AP2 version 8.7.96 (French Toast). You can then download the "ol8-iso-upload.sh" script and "el8.iso" file from the ScienceLogic Support portal, upload the ISO file, and push it to your collectors. For full instructions, see the OL8 Conversion Resource Center on the ScienceLogic Support portal, which includes links to resources such as the Oracle Linux 8 Conversion Guide.

On the Collector Groups page, the Status column will indicate which collector groups require staging by displaying "OL8 Staging Required".

The updates to the Collector Groups page are user-interface only and will not drive any functionality until a future SL1 release.

For more information: See the section on Collector Groups in the System Administration manual.

Events

What's new: SL1 now displays Skylar AI sourced events in event tables. Added Skylar AI under the Type column on all event inventory tables. You can also select Skylar AI as an event source in the Match Logic tab of the Event Policy Editor page. In doing so, you can select Skylar AI under the Event Source drop-down field on this page.

The Beta version of Skylar AI does not support collection labels in SL1 when selecting metrics to generate alerts.

For more information: See the section on The Match Logic Tab in the Events manual.

Additional New Features and Enhancements for French Toast

Business Services

The Business Services page now uses a new GraphQL query that uses machine learning to collect metric anomalies for your devices.

Devices

When deleting one or more devices that have associated asset records, you now have the option to delete the associated assets at the same time.

User Interface

Added a footer to the user interface that includes the current SL1 version and build number. Optionally, if you have selected the Display Previous Login In Footer checkbox on the Behavior Settings page (System > Settings > Behavior), this footer can also display the time stamp of your last successful or failed login attempt.

Security Features

The French Toast release for AP2 version 8.7.96 includes package updates to improve security and system performance.
12.2.2 FedRamp deployment on Amazon RDS will enforce that all connections made to the MySQL database must use TLS. The "nextui" service is now responsible for regulating all secure connections to the database.

Known Issues

The following known issues affect version 8.7.96 of the AP2 French Toast release:

Organizations must have at least one or more accounts assigned to them to ensure the relevant services are saved. (Jira ID: SLUI-17810)
The Relationships widget on the Device Investigator page currently does not display any visual data. (Jira ID: SLUI-20266)
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)
In some cases, after you create or override device relationships in maps in the default user interface (AP2), the GraphQL relatedNodes operation is returning NULL rather than retrieving the relationship as expected. (Jira ID: SLUI-19786)
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)

The current solution to this issue is to edit the service you wish to configure by manually updating the RCA Options field to RCA Enabled (contributors only).

For services that have their RCA Options field enabled, and has had a child service 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)

The current solution to this issue is to select the checkbox next to the device(s) you want to delete, click Delete Devices to open the Delete Devices modal, 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

}