Skylar One AP2 Nougat version 8.29.41 Release Notes

The Nougat release for AP2 version 8.29.41 introduces the following new features and enhancements:

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

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 Nougat, ensure you are running one of the following Skylar One versions:

  • 12.3.6 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 Nougat 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 Nougat

To install AP2 Nougat version 8.29.41 on to your system, you must download and install the AP2 Nougat TGZ bundle file from the ScienceLogic Support Center. 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 Nougat on a Database Server. These steps are also applicable to other AP2 hosting systems.

To install AP2 Nougat version 8.29.41:

  1. If you have not already done so, install or upgrade your Skylar One system to version 12.3.6 or above. For more information about upgrading to those releases, see the appropriate Skylar One platform release notes.

  2. Go to the ScienceLogic Support Center and download the Nougat TGZ file locally to your machine from the AP2 Release Versions page (Skylar One > Downloads > AP2 Releases). To do so, select "Nougat" 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.

  3. 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:

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

      where:

      • <aws-system-pem> is the PEM file for the AWS system.
      • <nougat-ap2-version> is the AP2 Nougat release version.
      • <system-ip-address> is the IP address of your Skylar One system.
    • For on-premises systems: At the shell prompt, copy the RPM file to your Skylar One system by running the following command:

    • scp -o StrictHostKeyChecking=no nextui-<nougat-ap2-version>.release.tgz em7admin@<system-ip-address>:/home/em7admin/

      where:

      • <nougat-ap2-version> is the AP2 Nougat release version.
      • <system-ip-address> is the IP address of your Skylar One system.
  4. 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:

    • tar -xzf nextui-<nougat-ap2-version>.release.tgz

      where <nougat-release-ap2-version> is the AP2 Nougat release version.

    • For TAR files:

    • tar -xf nextui-<nougat-ap2-version>.release.tar

      where <nougat-release-ap2-version> is the AP2 Nougat release version.

  5. Finish the installation by running the following commands:

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

    where <nougat-ap2-version> is the AP2 Nougat release version.

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

    where <nougat-ap2-version> is the AP2 Nougat release version.

  6. Enter y to confirm the installation of the AP2 RPM file.

  7. Reload the daemon service by running the following command:

    sudo systemctl daemon-reload

  8. 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 Nougat release features for AP2 version 8.29.41:

  1. If you are currently on Skylar One version 12.3.6 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 > Downloads > AP2 Releases) on the ScienceLogic Support Center. 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 Mochi release, download the RPM file labeled "Mochi".

  2. 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:

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

      where:

      • <aws-system-pem> is the PEM file for the AWS system.
      • <rollback-ap2-version> is the rollback AP2 version.
      • <system-ip-address> is the IP address of your Skylar One system.

    • For on-premises systems: At the shell prompt, copy the RPM file to your Skylar One system by running the following command:

    • scp -o StrictHostKeyChecking=no nextui-<rollback-ap2-version>.rpm em7admin@<system-ip-address>:/home/em7admin

      where:

      • <rollback-ap2-version> is the rollback AP2 version.
      • <system-ip-address> is the IP address of your Skylar One system.
  3. 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.

  4. Reload the daemon service by running the following command:

    sudo systemctl daemon-reload

  5. Restart the NextUI service by running the following command:

    sudo systemctl restart nextui.service

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

New Features and Enhancements in AP2 Nougat version 8.29.41

This section describes the features and enhancements that are included in Skylar One AP2 Nougat version 8.29.41.

Business Services

  • What's new: Updates to the Service Investigator pages. The following updates were made to reflect the rebranding of other ScienceLogic products:

    • The Skylar AI heading under the Timeline panel is now Skylar Advisor.

    • The RestorePoint tab under the Changes heading of the Timeline panel is now Skylar Compliance.

    • The Skylar AI tab under the Events panel is now Skylar Advisor.

Devices

  • What's new: Enhanced Topology Settings. Added new topology options at the device level in AP2 that make it easier for Skylar One to form relationships between devices. These four fields on the Settings tab of the Device Investigator enable you to set enhanced Layer-2, Layer-3, Cisco Discovery Protocol (CDP), and Link Layer Discovery Protocol (LLDP) topology processing options for individual devices. This enhancement enables Skylar One to provide additional context about device relationships, better topology maps, and enhanced event correlation.

    • For more information: See the section on The Settings Tab in the Device Management manual.

Maps

  • What's new: Introduction to Geographic Maps for Business Services. You can now create geographic maps for business services. The following updates were made to support this new feature:

    In the AP2 Nougat release, version 102 of the "ScienceLogic: Geographic Maps" PowerPack includes an additional report that must be run to plot Business Services. A new bulk upload script for Business Services will also be available on the ScienceLogic Support Center. These items will not be available immediately at launch; they are expected to be released about a week after the AP2 Nougat release went live. For more information, refer to the Managing Geographic Maps section of the Maps manual.

    • When creating a geographic map, you can use the Entity Type field to choose whether to plot business services or devices. The available options in this field are:

      • Services. Select this option to create a geographic map based on the locations of business services.

      • Devices. Select this option to create a geographic map based on the locations of devices.

    • The following columns were added to the Geographic Maps page (Maps > Geographic Maps) to enhance map visibility and tracking:
      • Created By. The username of the person who originally created the map.
      • Last Edited By. The username of the last person who modified the map.
      • Date Edited. The most recent date the map was edited.
      • Date Created. The date the map was created.
      • Map Entity. Specifies whether the map plots devices or services as entities.
      • ID. The ID associated with the geographic map.
    • For more information: See the section on Geographic Maps in the Maps manual.

Additional New Features and Enhancements for Nougat

Events

  • Updated the visuals for the event severity filter at the top of the Events page. You can now more clearly see which severity levels are selected or not when filtering the table of events.

Global Manager

  • Stack-level authentication is now enabled by default for Global Manager systems, and no longer requires you to manually add feature toggles during setup.

GraphQL (GQL)

  • To support the new enhanced topology feature, added the following topology-related fields to the "updateDevice" mutation, "devices" query, and "deviceClasses" query in GQL:
    • l3_topo
    • lldp_topo
    • cdp_topo
    • l2_topo
  • Added a new "businessServiceInsights" GQL query to provide visibility into business service adoption and performance. This endpoint returns key metrics such as:
    • Total number of services
    • Counts of root, shared, device, disabled, maintenance, and orphaned services
    • Device services with no associated devices
    • Top 10 services by device count
    • Number of policies using Dynamic Applications
    • Number of Dynamic Application metrics collected per run
  • To support upcoming device merge and unmerge functionality in AP2, added the following new items in GQL:
    • mergeDevices mutation
    • unmergeDevices mutation
    • mergedDevice field to the Device entity
    • hasMergedDevice search parameter
    • isMergablePhysicalDevice and isMergableComponenetDevice boolean searches to the device GQL query
  • Made the following changes related to account policies:
    • "AccountPolicy" mutations now consider Globally Unique Identifier (GUID) headers and system IDs, ensuring only the owning system can mutate records and that GUIDs are set correctly.
    • The "updateAccountPolicy" mutation now supports all account policy fields and enables you to apply policies to all users with a single action.
    • "AccountPolicy" and "Organization" mutations can now be globally managed, so updates and deletions are properly controlled and propagated across stacks.
    • Added a new "applyAccountPolicyToAccounts" mutation that allows you to apply an account policy to all aligned accounts.
  • Made the following changes related to Global Manager credentials:
    • Added a new "createGlobalManagerStackCredential" mutation which lets you create and align a new credential to a Global Manager stack in one step.
    • Replaced the "alignGlobalManagerCredential" mutation with "alignGlobalManagerStackCredential".
    • Added a new "unalignGlobalManagerStackCredential" mutation to unalign a credential to a Global Manager stack.
  • Removed the "AccessKey.hooks" field and "hooks" argument from the "createAccessKey" and "updateAccessKey" mutations, and were replaced with the "accessKeyHooks" field.
  • Added the ability to filter GQL queries and mutations by minimum platform version at the field and argument level.
  • You can now control whether only signed PowerPacks can be installed using the new "requireSignedPowerPack" field in the "systemSettings" resource. On FIPS-compliant systems, this setting is always true and cannot be changed. The new "updateRequireSignedPowerPack" mutation allows administrators to adjust this setting on non-FIPS systems.
  • To make GPG key management easier, added a new "GpgPublicKey" resource, along with the "gpgPublicKey" and "gpgPublicKeys" queries to view public keys and the "importGpgPublicKey" and "deleteGpgPublicKeys" mutations to import or remove keys.
  • You can now use the "classicReport" and "classicReports" queries to retrieve reports by ID, name, and PowerPack alignment, or to find reports not linked to any PowerPack.
  • Updated the "credentialFields" query to allow searches for PowerPack alignment.
  • The "ownerSystemId" field is now exposed as read-only on globally managed queries, making it clear which system owns each record.

Skylar AI

  • When a Skylar AI service connection is deleted, the Skylar management script will run automatically to stop data export and reset feature toggles.

User Interface

  • All references to "SL1" in the Node Configuration Utility have been updated to "Skylar One".

Issues Addressed in Skylar One AP2 Nougat version 8.29.41

This section describes the issues that were addressed in Skylar One AP2 Nougat version 8.29.41.

Business Services

  • Addressed an issue where services deleted prior to the AP2 Lokma release were still appearing in the "data_har" database despite their removal. (Jira ID: SLUI-21757)
  • Fixed an issue where severity chips for healthy events were not displaying when Cleared Events was selected from the Log Insights tab under the Skylar AI section of the Timeline panel on the Service Investigator page. Now, cleared Skylar Automated RCA events correctly show severity chips for healthy events. (Jira ID: SLUI-22256)

Credentials

  • Resolved an issue in the Create Credential modal that appears when creating an AWS credential, where the modal incorrectly displayed the Enable FIPS Endpoint and Enable SSL Verification for the SL1 API toggles. (Case: 00523734) (Jira ID: SOL-29705)
  • Resolved an issue where the Credentials page occasionally did not load or display all credentials as expected. (Case: 00551140) (Jira ID: SLUI-22673)
  • When defining or editing a credential in the Credential Tester panel of the Edit Credential modal on the Credentials page, the Select Credential Test field displays only the credential tests relevant to the selected credential type. (Case: 00526225) (Jira ID: SLUI-22371)

Dashboards

  • When creating or editing Interfaces widgets and selecting Heat in the Type field under the Metrics & Properties column of the Create Widget page, the heat map will display as expected after saving. (Case: 00552693) (Jira ID: SLUI-22686)
  • Resolved an issue where editing and saving the Collection State column in Interfaces widgets on the Dashboards page could cause widget data to disappear. (Jira ID: SLUI-22777)
  • Fixed an issue where a dashboard created and shared by an admin could lose its shared organization settings and show an error if a non-admin user edited and saved it; dashboards now retain their sharing settings after edits by any user. (Jira ID: SLUI-22691)
  • Resolved an issue where toggling on This widget can drive other widgets in a Device widget with Table visualization, while creating or editing a dashboard, caused selected checkboxes to blink in the Preview pane. (Jira ID: SLUI-22678)
  • Resolved an issue on the Dashboards page where dashboards could not be shared with organizations other than “System” using the Visibility column in Global Manager; sharing now works for all organizations. (Jira ID: SLUI-22669)
  • Addressed an issue where the Scale prefix field appeared twice when adding metrics and properties to a widget; the prefix now displays correctly for both new and existing widgets. (Jira ID: SLUI-22508)

Devices

  • Fixed an issue where devices could not be aligned to any organization other than “System” when Global Manager mode was disabled. (Jira ID: SLUI-22664)
  • Improved the Anomaly Chart modal on the Anomaly Detection tab of the Devices page by adding visual dividers and updating tooltips. The top chart shows only anomaly scores and the bottom chart displays metric values and expected ranges with units. (Jira ID: SLUI-22379)

Events

  • The Categorize events with an external system field in Advanced tab of the Event Policy Editor page (Events > Event Policies > create or edit) now accepts alphanumeric, punctuation, and special characters as intended. (Case: 00553372) (Jira ID: SLUI-22657)
  • The event policy editor now works correctly if you have event policy permissions, regardless of your Dynamic Application access. (Case: 00534604) (Jira ID: SLUI-22583)
  • Fixed an issue where the Edit Note button on the Events page did not function when multiple events were selected for note editing in Global Manager systems. (Jira ID: SLUI-21131)
  • Improved the visibility of the Cancel button on the Event Policies page when using Dark Mode, making it easier to see and interact with the button. (Jira ID: SLUI-22338)

Global Manager

  • Fixed an issue where duplicated dashboards in Global Manager mode not appearing in the correct listing page; now, all dashboards display as expected after duplication. (Jira ID: SLUI-22784)

GraphQL

  • The "createEventPolicy" mutation now displays clear error messages when the source field is missing or invalid, allowing event policies to be created successfully through both the user interface and GraphQL. (Jira ID: SLUI-22550)
  • Fixed an issue where creating a universal credential using GraphQL could result in duplicate entries with the same type and subtype. The "CreateCredentialField" mutation now prevents duplicate credentials, and credentials can be created and edited correctly. (Jira ID: SLUI-22487)

Maps

  • Addressed an issue where the Organization field in the Geographic Maps creation page displayed an error message requiring an organization to be selected, even when one had already been chosen. (Jira ID: SLUI-22349)

Known Issues

The following known issues affect version 8.29.41 of the Skylar One AP2 Nougat release:

Business Services

  • 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, set the RCA Options field to Disabled for the parent service 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

  • 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 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 or editing a geographic map, filters applied in one map might be hidden if the related column is hidden in another map. To work around this issue, enable all columns by clicking the gear icon () to open the Grid Settings menu, select Column Preferences to open the Find column menu, then click "Show All". Alternatively, you can click the gear icon () next to the filter field (used to search devices or services), and select Clear. This prevents columns from being hidden or shown while preserving your applied filters. (Jira ID: SLUI-22809)

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)