SL1 AP2 Lokma version 8.20.70-45 Release Notes

The Lokma release for AP2 version 8.20.70-45 introduces several updates: enhanced refresh interval functionality for services on the Business Services page, improved data handling on the Devices page, refinements to the Event Policy Editor, and fixes for several issues from previous releases.

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

This release includes the following new features and enhancements:

The ability to set the refresh interval for services in bulk on the Business Services page
Enhanced data handling and visibility on the Devices page
Improvements to the Event Policy Editor
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 Lokma, ensure you are running one of the following SL1 versions:

12.3.0 and later

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 Lokma 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 Lokma

To install AP2 Lokma version 8.20.70-45 on to your system, you must download and install the AP2 Lokma TGZ bundle file from the ScienceLogic Support site.

The AP2 Lokma release requires downloading and installing a TGZ bundle, which contains three separate RPM files.

If you are using an on-premises system, you must install the AP2 and libem7 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 Lokma on a Database Server. These steps are also applicable to other AP2 hosting systems.

To install AP2 Lokma version 8.20.70-45:

If you have not already done so, install or upgrade your SL1 system to version 12.3.0 or above. For more information about upgrading to those releases, see the appropriate SL1 platform release notes.
Go to the ScienceLogic Support site and download the Lokma TGZ file locally to your machine from the AP2 Release Versions page (Product Downloads > SL1 Platform Downloads > AP2 Releases). To do so, select "Lokma" from the Release Files table and then click the Download File button located under the Release File Downloads section of the page.
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 TGZ file on the Database Servers and the Administration Portal by running the following commands on those systems:

tar -xzf nextui-<lokma-ap2-version>.release.tgz

where <lokma-release-ap2-version> is the AP2 Lokma release version.

cd nextui-<ap2-version>.release

where ap2-version> is the AP2 Lokma release version.

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

where <ap2-version> is the AP2 Lokma 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 Lokma release features for AP2 version 8.20.70-45:

If you are currently on SL1 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 (Product Downloads > SL1 Platform Downloads > 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 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.
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 Lokma version 8.20.70-45

This section describes the features and enhancements that are included in SL1 AP2 Lokma version 8.20.70-45.

Business Services

What's new: Services refresh interval updates. You can now update the refresh interval for services in bulk on the Business Services page. To do so, select the checkboxes next to the services you want to update, then select Update Refresh Interval from the Actions field.

Additional Business Services Updates

Updated the default service policy condition values for both health and risk values.

Devices

What's new: Enhanced data handling and visibility on the Devices page. The following updates were made to support this enhancement:
- You can now filter the list of devices that appear on the Devices page based on their values in the SNMP Credential and SNMP Version columns.
- Added a new SL Agent column to the Devices page. This column, which is hidden by default, indicates whether an SL1 agent is installed on the devices listed on the page. If an agent is installed on a device, you can click the Yes hyperlink in the SL Agent column to display a modal where you can update the agent's configuration.
- You can now manually create one or more physical devices simultaneously by uploading a .csv file from the Devices page. To do so, click the drop-down arrow button next to the Add Devices button and select Create a Physical Device from File.

Events

What's new: Improvements to the Events Policy Editor. The following updates were made to support this enhancement:
- You can now align event policies to specific organizations on the Event Policy Editor page (Registry > Events > Event Manager > create or edit). All event policies are "Global" by default and apply to all devices unless specified. To change the alignment of an event policy, click Global Policy, select the Specific Organizations radio button, select the checkbox next to each organization to which you want to align the event policy, and then click the Apply button.
- Added a notification window to the Event Policy Editor page (Registry > Events > Event Manager > create or edit) that explains the new organization alignment feature. The notification window will display when creating or editing an event policy. You can close the notification window or you can dismiss it permanently by selecting the Don't show this again checkbox.

Additional Events Updates

If you add a user display name to your account on the User Accounts page (Registry > Accounts > User Accounts), that display name now appears in place of your username in the following areas:
- On the Events page, under the Acknowledge column for acknowledged events.
- On the Event Policies page (Events > Event Policies), under the Edited By column.
- On the Event Investigator page, next to the Clear button for acknowledged events.
- On the Events and Events Details pages, when hovering your cursor over the Acknowledge button.
You can now filter the Acknowledge column on the Events page by displayed usernames.

Additional New Features and Enhancements for Lokma

Credentials

A Save As option is now available when editing a credential type in the Edit Credential Type modal (Manage > Credentials > Types > edit a credential type).

Dashboards

Improved widget visualizations and interactivity by upgrading the Highcharts integration to version 12.2.

Global Manager

When running on a Global Manager stack, the "createDeviceCategory" mutation, by default, creates the device category on the Global Manager stack as well as on the enabled child stacks. New child stacks and modifications to the "mutateGlobalManager" mutation can alter this behavior, allowing it to be executed in the following ways:
- Locally (on the Global Manager only)
- Remotely (on one or more child stacks only)
- Locally and remotely (on selected subsets of child stacks)

GraphQL

Removed deprecated timer functions from multiple GraphQL resources related to devices and Dynamic Applications.
Added "lastValue" and "metrics" functions to the "monitorWebContents" query in GraphQL, enabling the Dashboards page to query a set of monitoring policies and retrieve the last value from monitorMetric data on the device associated with those policies.
You can now use "skylarConnectorStatus" to query the latest status of the Skylar management script when it is being created or updated.
Ensured that the "executeDeleteDevices" GraphQL mutation indicates an error when you attempt to delete a device and the deletion fails.

Skylar AI

Updated all references of "Zebrium" to "Skylar RCA" on the Service Connections page (Manage > Service Connections).
After creating or editing a Skylar AI service connection, a modal now appears with a "Select Organizations" link that navigates to the Organizational Account Administration page to encourage setting up organization export to Skylar AI. This modal can be closed if you want to set up organization export to Skylar AI later.
You can now use "skylarConnectorStatus" to query the latest status of the Skylar management script when it is being created or updated.
Added the following mutations, which are accessible to only users with administrator privileges:
- checkSkylarConnector
- enableSkylarConnector
- pauseSkylarConnector
Added three new columns to the Service Connections page (Manage > Service Connections):
- Service Check, which displays the Run Test button if the service type is "Skylar AI Engine". Clicking Run Test runs a script to check the status of the Skylar AI connection and display the results in a modal.
- Status, which displays one of the following values depending on the results of the latest service connection test:
  - Status Unknown.
  - Enabled. Exporting.
  - Enabled. Not Exporting.
  - Exporting Paused.
- Status Updated, which displays the date and time the service connection was last tested.

Issues Addressed in SL1 AP2 Lokma version 8.20.70-45

This section describes the issues that were addressed in SL1 AP2 Lokma version 8.20.70-45.

Devices

The Collector Groups page (Manage > Collector Groups) now displays the correct number of Data Collectors in a collector group, rather than incorrectly indicating a maximum of 10 Data Collectors per collector group. (Case: 00501726) (Jira ID: SLUI-21874)
Resolved an issue where searching for the location of an asset or device on the Asset Manager page (Registry > Assets > Asset Manager) resulted in an error. (Case: 00500159) (Jira ID: SLUI-21765)

Dashboards

Resolved an issue where performance metric references in dashboard widgets could display incorrect or blank values when the dashboard was installed through a PowerPack. (Case: 00494949) (Jira IDs: SLUI-21486, SLUI-22044)
Resolved an issue where auto-refreshing on the Dashboards page was not keeping user sessions active, even when the Page Auto-Refresh Keeps User Session Active field was set to Enabled on the Behavior Settings page (System > Settings> Behavior). (Case: 00503563) (Jira ID: SLUI-21787)

Events

Resolved an issue where users with limited permissions might have encountered an error message when clicking the Actions button (the ellipses icon) at the following locations: (Case: 00498124) (Jira IDs: SLUI-21788, SLUI-21866)
- The top-right corner of the Event Overview panel of the Event Investigator page
- The Events table that appears on the Events page, Service Investigator page, or Device Investigator page
- The Changes table on the Service Investigator page
- The Log Insights table on the Service Investigator page.

GraphQL

Resolved an issue that caused device GraphQL queries based on interfaces to fail. (Case: 00513430) (Jira IDs: SLUI-22069, SLUI-21560)
Resolved an issue where the "createDiscoverySession" GraphQL mutation produced an error when upgrading SL1 to version 11.3.1. (Case: 00360478) (Jira ID: SLUI-21434)

Known Issues

The following known issues affect version 8.20.70-45 of the AP2 Lokma release:

Business Services

Deleted services continue to appear in the "data_har" database even after they have been removed. (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, 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 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 SL1 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 that 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)

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)
On the Devices page, devices are unable to align with newly created organizations. (Jira ID: SLUI-20941)
The columns on the Events tab of the Device Investigator page cannot be sorted. (Jira ID: SLUI-20991)
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)

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)

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 SL1 server console: "Variable "$procId" of non-null type "ID!" must not be null." (Jira ID: SLUI-21070)

Skylar AI

When creating a Skylar AI service connection from the Service Connections page (Manage > Service Connections), it does not appear in the left sidebar on the Skylar AI page, even after saving it. (Jira ID: SLUI-22176)

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 SL1 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)