Skylar One AP2 Mochi version 8.26.4-45 Release Notes

With the Mochi release for AP2 version 8.26.4-45, SL1 is now rebranded as Skylar One. This change is reflected throughout the user interface. In addition, the Mochi release includes several updates, including a new Geographic Maps page for the creation of custom geographic maps and quick, location-based insights on devices; and several addressed issues to enhance stability and performance.

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

This release includes the following new features and enhancements:

An official rebranding of "SL1" to "Skylar One" in all areas of the user interface
A new Geographic Maps page where you can create custom geographic maps to visualize devices on a map and gain location-based insights
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 Mochi, ensure you are running one of the following Skylar One versions:

12.3.0 and later

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

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

Installing or Uninstalling AP2 Mochi

To install AP2 Mochi version 8.26.4-45 on to your system, you must download and install the AP2 Mochi TGZ bundle file from the ScienceLogic Support site. This bundle contains three separate RPM files. If you are using an on-premises system, you must install the AP2 RPM files on all systems, including the Database Server and the Administration Portal, if applicable. For AWS systems, you must install the RPM files on all relevant data engines.

The following instructions provide an example for installing AP2 Mochi on a Database Server. These steps are also applicable to other AP2 hosting systems.

To install AP2 Mochi version 8.26.4-45:

If you have not already done so, install or upgrade your Skylar One system to version 12.3.0 or above. For more information about upgrading to those releases, see the appropriate Skylar One platform release notes.
Go to the ScienceLogic Support site and download the Mochi TGZ file locally to your machine from the AP2 Release Versions page (Skylar One > Support > AP2 Releases). To do so, select "Mochi" from the Release Files table and then click the Download File button located under the Release File Downloads section of the page.

Depending on your browser or operating system, the TGZ file might download as a TAR file.
Install the AP2 TGZ or TAR file on the Database Servers and the Administration Portal by running the following commands on those systems:
- For TGZ files:
- For TAR files:
Either go to the console of the Skylar One 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:
Finish the installation by running the following commands:

cd nextui-<mochi-ap2-version>.release

where <mochi-ap2-version> is the AP2 Mochi release version.

sudo sh install-nextui-<mochi-ap2-version>.release.sh

where <mochi-ap2-version> is the AP2 Mochi 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 Mochi release features for AP2 version 8.26.4-45:

If you are currently on Skylar One version 12.3.0 or above and want to roll back to a previously installed AP2 release, download the RPM file for that earlier release from the AP2 Release Versions page (Skylar One > Support > AP2 Releases) on the ScienceLogic Support site. To do so, select the name of the AP2 release you want to roll back to from the Release Files table and then click the Download File button located under the Release File Downloads section of the page.

For example, if you want to roll back to the AP2 Key Lime Pie release, download the RPM file labeled "Key Lime Pie".
After you have the AP2 RPM files downloaded locally, either go to the console of the Skylar One Database Server or use SSH to access the Database Server.
- For AWS systems: At the shell prompt, copy the RPM file to your Skylar One system by running the following command:
- For on-premises systems: At the shell prompt, copy the RPM file to your Skylar One 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.
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.

New Features and Enhancements in AP2 Mochi version 8.26.4-45

This section describes the features and enhancements that are included in Skylar One AP2 Mochi version 8.26.4-45.

Rebranding

What's new: SL1 is now Skylar One! With this release, ScienceLogic has rebranded SL1 to Skylar One. You will notice this rebranding throughout the platform. This change, as well as similar branding changes to the other products offered by ScienceLogic, reflects ScienceLogic's commitment to delivering intelligence that accelerates outcomes through service-centric observability, AI-driven operations, and intelligent automation.
For more information:See the ScienceLogic website (https://sciencelogic.com/platform/overview).

Maps

What's new: Introduction to Geographic Maps. A new Geographic Maps page (Maps > Geographic Maps) allows you to create and manage custom geographic maps that visualize devices on a map and provide location-based insights of those devices at a glance. The following updates were made to support this new feature:
- A sortable, filterable table on the Geographic Maps page lists all geographical maps associated with your organization. The table consists of three columns:
  - Map name. The name of the geographical map.
  - Organization. The entity or organization to which the associated geographical map is aligned.
  - Map Region. The geographic area (countries and states).
- You can create custom geographic maps from your existing devices from the Geographic Maps page by selecting devices that have been associated with a location. If no devices are available for selection, you will need to load location data first. In this release, location data can be uploaded in bulk, and this process can be repeated at any time to add more location data to devices. Once the location data for devices are added, they will appear as options when creating a new map.
- Geographic maps include the following interactive capabilities that allow you to engage with mapped devices directly and explore device data visually:
  - Hover behavior: When you hover your cursor over a node, it displays a list of all devices (by device name) associated with that location.
  - Zoom behavior: If multiple locations with devices are in close proximity, the map displays a single node showing the number of locations in that area. As you zoom in, the clustered node separates into individual nodes labeled by their specific location names. You can then hover your cursor over each location-specific node to see the devices in that particular area.
  - Single-location behavior: If there is only one location with devices in a region of the map, even when zoomed out, the map will display a single node marked by that location's name. Hovering over it with your cursor will show all devices in that location.

Additional New Features and Enhancements for Mochi

Business Services

Updated the swim lane headers in the Timeline panel of the Service Investigator page by adjusting text size and adding divider lines to create a clearer visual distinction between different header sections.
The Policy column now displays by default on the Business Services page.

Devices

Changed the default sort on the page from Last Modified to Anomaly Count on the Anomaly Detection tab of the Device Investigator, to sort the items on the page from the most number of anomalies to the least by default.

GraphQL

Removed the "createFeatureToggle" and "deleteFeatureToggle" mutations.
You can now create account policies using the "createAccountPolicy" mutation.

Skylar AI

Updating the nextui.conf file in the Database Server, changes are automatically replicated to the Administration Portal.
After clicking the Run Test button for a service connection, the Skylar Connection Debug modal will now appear and display the script's status output. You can re-run the status check by clicking the Run Again button.

User Interface

The About page now displays the AP2 release version name in addition to the existing AP2 release version number. The release name also appears for hotfix versions within the same release.
Updated the classic ScienceLogic favicon that displays in the tab of your web browser to the current short-form ScienceLogic logo.

Issues Addressed in Skylar One AP2 Mochi version 8.26.4-45

This section describes the issues that were addressed in Skylar One AP2 Mochi version 8.26.4-45.

Credentials

Resolved an issue in the Edit Credential modal where, when editing or testing a credential, the Select Credential test field in the Credential Tester panel wasn't showing the full list of credential tests. (Case: 00517459) (Jira ID: SLUI-22132)

Dashboards

Resolved an issue where Device widgets using the Line Chart visualization couldn't be saved when a negative value was entered in the Threshold Line field. (Case: 00488189) (Jira ID: SLUI-22119)
Resolved an issue where selecting multiple devices for widgets using the Forecast visualization did not display information for all selected devices. (Case: 00526493) (Jira ID: SLUI-22344)
Addressed an issue on the Dashboards page where widgets using the Table or Bar Chart visualizations did not update when the time span was adjusted. (Case: 00515942) (Jira ID: SLUI-22260)

Devices

Resolved an issue that caused a search on collectionState in the getInterfaces GQL query to return an error. (Case: 00523713) (Jira ID: SLUI-22466)
Resolved an issue that prevented the columns on the Events tab of the Device Investigator from being sortable. (Jira ID: SLUI-20991)

Events

Addressed an issue that prevented event notes from displaying in the exported CSV file created from the Events page or the Event Dashboard widget. (Case: 00523119) (Jira ID: SLUI-22340)
Updated the "notifierLogs" GraphQL query so that when an event search is executed, it will only return logs for events with event IDs included in the filter. (Case: 00524845) (Jira ID: SLUI-22340)

GraphQL

Fixed an issue where creating discovery sessions using the "createDiscoverySession" GraphQL mutation resulted in an error and the discovery session wasn't created. (Case: 00511630) (Jira ID: SLUI-22182)
Resolved an issue where GraphQL queries returned null results when searching for an organization with a null value, which caused an error during the query execution. (Case: 00522745) (Jira ID: SLUI-22442)

Skylar AI

Resolved an issue where Skylar AI service connections created from the Service Connections page (Manage > Service Connections) did not appear in the left sidebar of the Skylar AI page. (Jira ID: SLUI-22176)
Addressed an issue where the Skylar Analytics Summary panel on the Events page did not display timeline charts showing Skylar AI's predictive alert data. (Jira ID: SLUI-22761)

Known Issues

The following known issues affect version 8.26.4-45 of the Skylar One AP2 Mochi release:

Business Services

Services deleted prior to the AP2 Lokma release are still appearing in the "data_har" database despite their removal. (Jira ID: SLUI-21159)
Organizations must have one or more accounts assigned to them to ensure the relevant services are saved. (Jira ID: SLUI-17810)
For services where the RCA Options field is enabled and a child service has been removed, Skylar One 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 three-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.

Credentials

The Credentials page in the default user interface (AP2) fails to display credentials that are not aligned with an organization, but displays these credentials correctly in the classic user interface on the Credential Management page. (Jira ID: SLUI-20947)
On the Credentials page, if you have more than 50 credentials and at least one of the first 50 credentials is not aligned with an organization, the page will display duplicates of these credentials. (Jira ID: SLUI-20947)

Dashboards

If you open the default "Server" dashboard, you might receive an error on the page as well as in the Total Network Traffic widget. (Jira ID: SLUI-21831)
Creating an Interface widget with the Leaderboard visualization, applying an advanced filter, and adjusting the data time span using the Time span filter results in an error. (Jira ID: SLUI-22200)
When editing the scale prefix of a Device widget using the Leaderboard visualization, the Storage Used column does not update in that widget's table. (Jira ID: SLUI-22198)
When editing an Events widget and setting the Refresh Mode field to None, the widget's events table shows the refresh mode as automatic, despite the change. (Jira ID: SLUI-21947)
When creating a Devices widget using the Line Chart visualization, toggling on Area Chart and then selecting either Percentage or Normal from the Stack Options field causes the line chart to not display. (Jira ID: SLUI-22592)
On the Dashboards page, when editing a widget using the Line Chart visualization, deleting the default "0" in the Threshold Line field prevents the widget from being saved. (Jira ID: SLUI-22591)

Device Management

On the Devices page, when sorting your search by the Organization column, the inventory table will sort by Organization ID instead. (Jira ID: SLUI-21459)
The assigned organization for devices might not always update, even after performing a bulk alignment organization action on the Devices page. To work around this issue, refresh your browser immediately after completing the bulk alignment action. (Jira ID: SLUI-21483)
The column widths on the Device Investigator page do not adjust when resized. (Jira ID: SLUI-20081)
Filtering the Collector Groups column on the Device Investigator page with multiple group names can cause the page to not load correctly. (Jira ID: SLUI-21035)
When sorting by columns on the Device Investigator page in Firefox, the table might continuously attempt to retrieve results unsuccessfully. (Jira ID: SLUI-21095)
The Device Categories page (Devices > Device Categories) fails to load properly whenever there is a category with a null ID. To work around this issue, go to the Device Categories page (System > Customize > Device Categories), locate the category with the null ID, and then remove that category by clicking the delete icon () next to the category. (Jira ID: SLUI-20731)
On the Devices page, the Clear Filters option does not remove search filters from the Asset ID column and does not update whenever the page is reloaded. To work around this issue, click the Select columns icon () on the Devices page, select Column Preferences, and then click Show All. Once you have done so, you can click the Select columns icon again and then select Clear Filters from the drop-down menu. (Jira ID: SLUI-20779)
The number of unacknowledged events in the Device Overview panel of the Device Investigator page does not update despite acknowledging alerts on a device. To work around this issue, add a new "unackEvents" subquery to the "Device Insights" query, then use that subquery to collect and retrieve information on unacknowledged events. (Case: 00471966) (Jira ID: SLUI-20858)
When deleting a device from the Devices page, the Delete Devices confirmation modal displays an error message instead of the usual confirmation text. Clicking OK still complete the deletion successfully. (Jira ID: SLUI-22538)

Events

The Edit Note button on the Events page does not work when multiple events are selected for editing notes in Global Manager. (Jira ID: SLUI-21131)
The events on the Events page cannot be sorted by the Organization column. (Jira ID: SLUI-20903)
From the Event Policies page (Events > Event Policies), you can delete only a single event policy at a time, even if you select multiple event policies for bulk deletion. (Jira ID: SLUI-20853)

Global Manager

The devices on the Devices page in Global Manager systems cannot be sorted by the IP Address column. (Jira ID: SLUI-21108)
On Global Manager systems, the View Event Policy option in the Actions menu () on the Events page does not work as expected. (Jira ID: SLUI-21133)
On Global Manager systems, the Events page does not display events from child stacks. To work around this issue, clear all system caches on both the child stacks and the Global Manager parent stack, then restart the NextUI service. (Jira ID: SLUI-21134)
On Global Manager systems, the ID column in organization widgets and device widgets now displays the organization's GUID rather than the stack ID and organization ID as intended. (Jira ID: SLUI-22654)

GraphQL

The "harProviderOnDemanProcessing" GQL query incorrectly creates a service table in the "data_har" database when executed with invalid or non-existent service IDs. (Jira ID: SLUI-21135)
Clicking the Run Now button for any Dynamic Application on the Collections tab of the Device Investigator will display the following GQL error message in the Skylar One server console: "Variable "$procId" of non-null type "ID!" must not be null." (Jira ID: SLUI-21070)

Maps

When creating a new geographic map from the Geographic Maps page (Maps > Geographic Maps), the Organization field shows an error message requiring an organization to be selected, even if one is already chosen. (Jira ID: SLUI-22349)

System Administration

When editing a collector group from the Collector Groups page (Manage > Collector Groups) by clicking its Actions menu (ellipsis icon) and unchecking two or more organizations in the Limit access to specific organizations field of the Edit Collector Group modal, the Organizations column on the Collector Groups page will show that only one organization was deselected, even if multiple were. (Jira ID: SLUI-22167)
Message Collectors on the Collector Groups page (Manage > Collector Groups) cannot be sorted by the Message Collectors column. (Jira ID: SLUI-22099)

User Interface

On the Custom Attributes page (Manage > Custom Attributes), you might not be able to view more than the first 20 custom attributes unless you zoom in or change the size of your browser to force Skylar One to fetch additional attributes. (Jira ID: SLUI-21449)
Name changes to nodes on the Nodes page (Manage > Nodes) are not saved. (Jira ID: SLUI-22248)
When creating a custom base attribute from the Custom Attributes page (Manage > Custom Attributes) and selecting both Restrict this field to integers and Index this field radio buttons, an error message appears indicating the base attribute can not be created. (Jira ID: SLUI-22277)