SL1 AP2 Doughnut version 8.6.30 Release

The Doughnut release for AP2 version 8.6.30 includes feature enhancements to the Device Investigator, Device Investigator Layouts page, and the Enhanced Service Investigator page, including improved performances when managing events, new ways to view and access events, GraphQL updates to support the enhancements to Device Investigator layouts, and various bug fixes.

AP2 releases are separate from SL1 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

Ensure you are running version 12.1.1 or later on an Oracle Linux 8 (OL8) instance of SL1 before installing AP2 Doughnut.

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.1, 12.2.0, or 12.2.1. The AP2 Doughnut update must be administered to systems that host AP2. All SL1 systems must be on the same AP2 version.

Installing or Uninstalling AP2 Doughnut

If you are running SL1 version 12.2.1, 12.2.1.1, or later, you do not need to install AP2 Doughnut version 8.6.30; it is included in those versions by default. You can optionally install AP2 Doughnut version 8.6.30 if you are running SL1 version 12.1.1 or 12.2.0.

SL1 12.2.1 should be consumed only by users who are performing fresh installations of SL1. If you are upgrading from a previous release, you must download and upgrade to the upcoming 12.2.1.1 release.

ScienceLogic strongly recommends that you review the installation and upgrade instructions, important notes about upgrading SL1, and known issues for this release before installing or upgrading to SL1 12.2.1.1 or SL1 12.2.1, respectively.

To install AP2 Doughnut version 8.6.30:

  1. If you have not already done so, upgrade your SL1 system to either the 12.1.1 Oracle Linux 8 (OL8) release, 12.2.0, 12.2.1, or the 12.2.1.1 release. For more information about upgrading to those releases, see the appropriate SL1 platform release notes.  
    • If you are installing AP2 Doughnut version 8.6.30 on SL1 version 12.1.1, proceed to step 2.
    • If you are installing AP2 Doughnut version 8.6.30 on SL1 12.2.0, you can skip to step 5.
    • If you have already installed the libem7 RPM file from the ScienceLogic Support site, proceed to step 5.
    • If you are a STIG user on SL1 12.2.1, 12.2.1.1, or later, proceed to step 15.
  2. If you are installing AP2 Doughnut on SL1 version 12.2.1 or later, and you are not a STIG customer, you must download the libem7 RPM file locally to your machine from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBt4z000000GsHACA0/libem7
  3. Either go to the console of the SL1 Database Server or use SSH to access the Database Server.
  4. At the shell prompt, copy the RPM file to your SL1 system by running the following command:

    5. scp -i <aws-system-pem>.pem -o StrictHostKeyChecking=no libem7-ipcserver-0.2.0-1.el8.x86_64.rpm em7admin@<system-ip-address>:/home/em7admin/

    where:

    • aws-system-pem is the PEM file for the AWS system.
    • system-ip-address is the IP address of your SL1 system.
  5. Download the AP2 Doughnut RPM file locally from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL00000008nB0AQ/doughnut
  6. Either go to the console of the SL1 Database Server or use SSH to access the Database Server.
  7. At the shell prompt, copy the RPM file to the AWS system by running the following command:

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

    where:

    • aws-system-pem is the PEM file for the AWS system.
    • doughnut-release-ap2-version is the AP2 Doughnut release version.
    • system-ip-address is the IP address of your SL1 system.

  8. Install the AP2 RPM file on your system by running the following command:

    9. sudo yum install nextui-<doughnut-release-ap2-version>.rpm

    where doughnut-release-ap2-version is the AP2 Doughnut release version.

  9. Enter y to confirm the installation of the AP2 RPM file.
  10. Install the libem7 RPM file on your system by running the following command:

    11. sudo yum install libem7-ipserver-0.2.0-1.e18.x86_64.rpm

  11. Enter y to confirm the installation of the libem7 RPM file.
  12. After the installation of both RPM files is complete, run the following commands to reload the daemon service:

    13. sudo systemctl enable libem7.socket

    sudo systemctl start libem7

    sudo systemctl daemon-reload

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

    14. sudo systemctl restart nextui.service

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

  14. To confirm that AP2 Doughnut version 8.6.30 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.6.30.
  15. If you are a STIG customer, you will need to manually install the node.js file. To do so, continue to step 16.
  16. Download the OL8 baseOS package by running the following command:

    17. curl -O https://yum.oracle.com/repo/OracleLinux/OL8/baseos/latest/x86_64/getPackage/oraclelinux-release-el8-1.0-9.el8.x86_64.rpm

  17. Install the OL8 baseOS package to your device to get access to App Stream repositories by running the following command:

    18. sudo dnf install oraclelinux-release-el8-1.0-9.el8.x86_64.rpm

  18. Verify that the OL8 baseOS package is included in the App Stream repositories by running the following command:

    19. sudo dnf repolist

  19. Verify that "nodejs app stream" is included in the App Stream repositories by running the following command:

    20. sudo dnf module list --all nodejs

  20. Enable "nodejs:18" in the App Stream repositories by running the following command:

    21. sudo dnf module enable nodejs:18

  21. Install "node" in the App Stream repositories by running the following command:

    22. sudo dnf module install nodejs

  22. Verify that "global mode" can be found by running the following command:

    23. which node

  23. Create a systemd drop-in at /etc/systemd/system/nextui.service.d/fips.conf. This file should contain the following information:

    24. [Service]
    ExecStart
    ExecStart=/usr/bin/node /opt/em7/nextui/index.js

  24. After you have installed the OL8 baseOS package and created a systemd drop-in, run the following command to reload the daemon service:

    25. sudo systemctl daemon-reload

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

    26. sudo systemctl restart nextui.service

To uninstall the Doughnut release features for AP2 version 8.6.30:

  1. If you are uninstalling AP2 Doughnut version 8.6.30 from SL1 version 12.1.1, proceed to step 2. If you are uninstalling AP2 Doughnut version 8.6.30 from SL1 12.2.0, you can skip to step 5.
  2. If you are uninstalling AP2 Doughnut on SL1 version 12.1.1, you must download the 12.1.1 AP2 RPM file locally to your machine from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL00000002JZ0AY/nextui70012101-r351
  3. Either go to the console of the SL1 Database Server or use SSH to access the Database Server.
  4. At the shell prompt, copy the RPM file to the AWS system by running the following command:

    5. 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 Croissant version.
    • system-ip-address is the IP address of your SL1 system.
  5. If you are uninstalling AP2 Doughnut on SL1 version 12.2.0, you must download the AP2 Biscotti RPM file locally to your machine from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBt4z000000GsH0CAK/biscotti
  6. Either go to the console of the SL1 Database Server or use SSH to access the Database Server.
  7. At the shell prompt, copy the RPM file to the AWS system by running the following command:

    8. 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 Croissant version.
    • system-ip-address is the IP address of your SL1 system.
  8. Install the RPM file on your device by running the following command:

    9. sudo rpm -U --force --replacefiles <ga-ap2-releaseVersion>.rpm

    where ga-ap2-releaseVersion is the AP2 Croissant release version.

  9. After the installation is complete, run the following commands to reload the daemon service:

    10. sudo systemctl disable libem7.socket

    sudo systemctl stop libem7

    sudo systemctl deamon-reload

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

    sudo systemctl restart nextui.service

Important Upgrade Notes for AP2 Doughnut 8.6.30

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 Doughnut version 8.6.30

This section describes the features and enhancements that are included in SL1 AP2 Doughnut version 8.6.30.

Business Services

  • What's new: Enabled the Enhanced Service Investigator page by default. You can enable or disable the Enhanced Service Investigator page in the nextui.conf file, or through GraphQL mutations at any time.  
  • For more information: See the section on Using the Enhanced Service Investigator in the Business Services manual.

Devices

  • What's new: Optimized Device Investigator and Device Investigator Layouts accessibility. The Cleared Events query in the Device Investigator has been optimized to improve overall performance on Device Investigator pages that display a large number of events. Non-administrator users can now access the Device Investigator Layout page. When viewing details about a Device Investigator layout, the alignment type will now default to public or private based on the selection made in the most recently edited alignment.

    You can now delete one or more Device Investigator layouts from the Device Investigator Layout page if you have an access key that includes the DEVICE_INVESTIGATOR_REMOVE or DEVICE_DASH_EDIT access hooks aligned to your account.

    The following updates were made to support this enhancement:

    • Added a new Numeric ID column to the Collections tab of the Device Investigator that displays the numeric integer ID number of each Dynamic Application listed on the page. The numeric integer ID number can be used to correlate Dynamic Applications to their error logs.
    • The Relationships widget that was added to Device Investigator in the AP2 Croissant version 8.5.7 release is now hidden by default. You can enable the widget using the following GraphQL mutation:

      • updateFeatureToggle(id: "system:AP2_DEVICEDETAIL_RELATIONSHIP_TAB", value:"enabled")

      If you have previously installed the AP2 Croissant version 8.5.7 release, then when you install the AP2 Doughnut version 8.6.30 release, the Relationships widget will disappear from any existing Device Investigator layouts. To re-enable it, use the above GQL mutation.

  • For more information: See Using the Device Investigator.

Additional New Features and Enhancements for Doughnut

Global Manager

  • Enabled Security Assertion Markup Language (SAML) as an option for single-sign-on (SSO) authentication for Global Manager using GraphQL.

    To support single sign-on capabilities for Global Manager, the AP2 Doughnut version 8.6.30 includes a new credential field for Global Manager stack-related queries and mutations.

GraphQL

  • Added a new convertDynamicAppGuidToNumericId query that returns the numeric integer ID for a Dynamic Application from its GUID.
  • Added GraphQL support for a "run-as" header, x-sl-run-as, that enables administrators to run queries and mutations as a different, non-privileged user. This header is available for use to administrators only; any other users who attempt to use it will receive a 401 error.
  • Deprecated headers with the prefix "x-em7" and replaced them with "x-sl". In a future release, support for "x-em7" headers will be removed.

Issues Addressed in SL1 AP2 Doughnut version 8.6.30

This section describes the issues that were addressed in SL1 AP2 Doughnut version 8.6.30.

Devices

  • Optimized the Cleared events query, which improved the performance of the Device Investigator whenever a large number of events are present.(Case: 00413105) (Jira ID: SLUI-19177)

Events

  • Resolved an issue where if you disabled a user initiated action, it would still appear in the Tools widget and the Event Console modal on the Events Investigator page. (Case: 00411150) (Jira ID: SLUI-19024)

Known Issues

The following known issues affect version 8.6.30 of the AP2 Doughnut 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 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)
  • 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 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>") {

    id

    value

    }

    }