Skylar One AP2 Opera Cake version 8.34.20 Release Notes

The Opera Cake release for AP2 version 8.34.20 introduces several enhancements aimed at improving visibility, usability, and workflow efficiency across Anomaly Detection and location management for devices and services. These updates provide new insights into service health and performance, streamline how locations are created and managed directly in the Skylar One user interface, and refine alerting and metric management to deliver a more intuitive and reliable user experience.

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:

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 Opera Cake, ensure you are running one of the following Skylar One (SL1) 12.3.7 or 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 Opera Cake 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 Opera Cake

To install AP2 Opera Cake version 8.34.20 on to your system, you must download and install the AP2 Opera Cake 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 Opera Cake on a Database Server. These steps are also applicable to other AP2 hosting systems.

To install AP2 Opera Cake version 8.34.20:

  1. If you have not already done so, install or upgrade your Skylar One system to version 12.3.7 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 Opera Cake TGZ file locally to your machine from the AP2 Release Versions page (Skylar One > Downloads > AP2 Releases). To do so, select "Opera Cake" 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-<OperaCake-ap2-version>.release.tgz em7admin@<system-ip-address>:/home/em7admin/

      where:

      • <aws-system-pem> is the PEM file for the AWS system.
      • <OperaCake-ap2-version> is the AP2 Opera Cake 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-<OperaCake-ap2-version>.release.tgz em7admin@<system-ip-address>:/home/em7admin/

      where:

      • <OperaCake-ap2-version> is the AP2 Opera Cake 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-<OperaCake-ap2-version>.release.tgz

      where <OperaCake-release-ap2-version> is the AP2 Opera Cake release version.

    • For TAR files:

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

      where <OperaCake-release-ap2-version> is the AP2 Opera Cake release version.

  5. Finish the installation by running the following commands:

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

    where <OperaCake-ap2-version> is the AP2 Opera Cake release version.

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

    where <OperaCake-ap2-version> is the AP2 Opera Cake 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 Opera Cake release features for AP2 version 8.34.20:

  1. If you are currently on Skylar One version 12.3.7 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 Opera Cake version 8.34.20

This section describes the features and enhancements that are included in Skylar One AP2 Opera Cake version 8.34.20.

Maps

  • What's new: A new Locations page. Added a new Locations page (Manage > Locations) where you can create and manage locations for devices and business services directly in the Skylar One user interface. The Locations page lets you add locations, associate them with organizations, and assign devices or services without generating reports or using the bulk import process. You can align and un-align devices and services to locations directly from the Locations page (Manage > Locations). You can also filter, search, and manage alignments with real-time updates.

    • For more information: See the section on Locations in the Maps manual.

Skylar AI

  • What's new: Improvements to the Anomaly Detection page.The following updates were made to the Anomaly Detection page:

    • Clicking the Enable Alert Policies button now opens a modal that allows you to select devices, Dynamic Application metrics, and indexes on which you can enable alerting. This modal automatically filters out any devices that are not aligned to organizations that use Skylar AI.
    • Updated the modal for enabling and disabling metrics to ensure that the buttons for enabling or disabling alerting work as intended, and that enabling or disabling a metric updates the alerting state but keeps the metric visible.
    • For more information: See the section on Skylar Analytics: Anomaly Detection in the Skylar AI manual.

Additional Skylar AI Updates

  • Ensured that the Anomaly Detection Thresholds page refreshes as intended without appearing to save changes made on the page if you click Cancel.
  • Updated the manner in which the Skylar AI Insights count value is calculated for the Device Investigator . With this update, the value now reflects the sum of all open root cause analysis events (accepted, suggested, or custom) plus all open anomaly index score events plus all open predictive alert events. In addition, this value is now hidden entirely if your system is not connected to Skylar AI.

Additional New Features and Enhancements for Opera Cake

Business Services

  • When creating or editing service policy rules on the Service Investigator page, the preview graph now uses raw, hourly, or daily summarized data based on the selected timespan for more accurate results.

Events

  • Column filtering for base custom attributes was added to the table on the Events page and events-related dashboard widgets, allowing you to filter these columns using a new filter syntax and partial matches for both string and integer attribute types.

Global Manager

  • Added support for automatically creating an account on a Global Manager stack when a request includes the necessary user and policy information. If the account does not already exist, it is created and the request continues as that user. If account creation fails, an error is returned. This streamlines access management across connected stacks.

GraphQL (GQL)

  • Added a new parameter to the "deleteGeoLocations" GQL mutation, allowing you to delete geographic locations even if they have aligned entities (devices or services). When a location is deleted, any aligned entities are automatically unaligned, streamlining the removal process.
  • Added an "accountPolicy" GQL mutation that allows the Global Manager to claim or release ownership of an account policy record on a stack, enabling proper control over record edits and deletions.
  • Added three new mutations: "claimAccountPolicy", "claimAccessKey", and "claimOrganization". These mutations let Global Manager take control of existing records on a stack by updating their identifiers to match the Global Manager’s records. This enables unified management of account policies, access keys, and organization records across stacks.
  • Added a new "disableSkylarConnector" GQL mutation, allowing you to remotely schedule the Skylar management script to be disabled.
  • The "accountPolicies" GQL query now includes stackDiff and syncStatus fields on Global Manager, making it easier to identify differences in user policies.

Issues Addressed in Skylar One AP2 Opera Cake version 8.34.20

This section describes the issues that were addressed in Skylar One AP2 Opera Cake version 8.34.20.

Business Services

  • Fixed an issue where editing different service policy rules that use the same Dynamic Application but different metrics would display the wrong metric label on the Y-axis of the graph. Now, the correct metric label is shown for each rule when editing. (Case: 00562795) (Jira ID: SLUI-23118)
  • Addressed an issue where, for services with the RCA Options field enabled, removing a child service prevented Skylar One from computing health, availability, and risk values until the Service Topology Engine returned an updated topology, which occurred every 5 minutes by default. (Jira ID: SLUI-18853)

Credentials

  • Ensured that when adding or updating SSH credentials, changes are now saved correctly when a valid Privacy Enhanced Mail (PEM) key is entered. (Jira ID: SLUI-23324)

Dashboards

  • Ensured all relevant devices appear correctly in dashboard widgets and filters as intended. (Jira ID: SLUI-22960)
  • Updated the Dashboards page to ensure it remains stable and displays data correctly, regardless of the selected date and time range, even in dashboards with a high number of widgets using the chart visualization options. (Case: 00519023) (Jira ID: SLUI-22480)
  • Resolved an issue where File System widgets using the Line Chart visualization would sometimes display default data labels in the chart legend rather than the correct file system labels. (Case: 00498710) (Jira ID: SLUI-21890)
  • Ensured the default "Server" dashboard no longer displays errors on the page or in the Total Network Traffic widget. (Jira ID: SLUI-21831)

Global Manager

  • Limited users can now query all Global Manager stacks regardless of their organization alignment. With this fix, users are able to make requests to any stack from the Global Manager system, even when they are not aligned to the same organization as the stack's device, though the aligned device will remain hidden. (Case: 00588571) (Jira ID: SLUI-23168)
  • Resolved an issue that redirected users to child stacks via their IP address rather than the fully qualified domain name (FQDN) when clicking on a managed device hyperlink in Global Manager systems. (Case: 00571716) (Jira ID: SLUI-23073)

Known Issues

The following known issues affect version 8.34.20 of the Skylar One AP2 Opera Cake release:

Business Services

  • Organizations must have one or more accounts assigned to them to ensure the relevant services are saved. (Jira ID: SLUI-17810)
  • Devices or services might be aligned to multiple organizations if the organization assigned to a location changes, with only the latest alignment shown on the Locations page (Manage > Locations). (Jira ID: SLUI-23254)
  • Adjusting column widths on the Business Services page requires a page reload for changes to take effect. (Jira ID: SLUI-23115)
  • When creating a service from a template, the resulting service might receive a copy of the policies, even if the Make copy of policies checkbox is not selected. (Jira ID: SLUI-23102)
  • On the Create Service from Template page, when creating a service from a template, the Service Name field is not editable until an organization is selected. (Jira ID: SLUI-23099)
  • The filter to select devices or services during service creation from templates is not editable. (Jira ID: SLUI-23247)

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)
  • Some fields in the Create Credential modal for certain credential types do not display guidance text. (Jira ID: SLUI-23265)

Dashboards

  • 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 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)
  • When creating or editing a Devices widget using the Table visualization with the Title links to another page checkbox selected and Dashboards selected from the Link type field, removing the selected dashboard causes the Save Widget button to disable, preventing the widget from being saved. (Jira ID: SLUI-23172)
  • When editing a Devices or File Systems widgets using the Number visualization, toggling off Show the unit reveals an extra Show the prefix toggle that does not function if enabled or disabled. (Jira ID: SLUI-23147)
  • When a File Systems widget using the Leaderboard Bar Chart visualization is driving a subscribed table and multiple selections are made in the bar chart, the "%" unit label appears in the Data Used column of the table instead of the correct kilobyte (kB) unit. (Jira ID: SLUI-10317)
  • 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)
  • In Eventswidgets using the Table visualization, you cannot resize individual custom attribute columns nor reorder custom attributes using the drag-and-drop feature. (Jira ID: SLUI-23233)
  • 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)
  • 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)
  • When configuring widgets using the Table visualization that has specific selections, and later delete one or more of the selected entities from the platform, the deleted items might still appear in the widget configuration. (Jira ID: SLUI-23229)
  • When editing a widget in the Edit Widget modal, if a dashboard has a driving and subscribing widget connected by a custom context, toggling on the This widget can drive other widgets and then saving the widget causes the custom context to disappear from the context drop-down field when the toggle is re-enabled, even if the subscribing widget is still using that context. (Jira ID: SLUI-23151)
  • When using the Comfortable density setting in widgets using the Table visualization, the "Find column" menu under Column Preferences might not show the list of columns unless the widget is resized. (Jira ID: SLUI-23171)

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)
  • The Anomaly Detection tab appears in the Device Investigator even if the device is not collecting data for Skylar Analytics. (Jira ID: SLUI-23144)
  • You might experience an issue where the Devices page loads only the first 30 devices and otherwise continually indicates that the page is loading. (Jira ID: SLUI-23248)

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)
  • On the Event Categories page (Events > Categories), if the Correlation Time column has the maximum value (4294967295), it shows a dash (–) instead of the number. (Jira ID: SLUI-23346)

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: "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, click the gear icon (), select Column Preferences, and 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 are not saved on the Nodes page (Manage > Nodes). (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)
  • The filter for columns where you can select a date (such as on the Events or Event Policies pages) might show an error in the browser console when using the “Before,” “After,” or “At” options. (Jira ID: SLUI-23421)
  • The Skylar AI icon still appears in the basic menu even after the Skylar AI connection is disabled. (Jira ID: SLUI-23327)