SL1 AP2 Espresso version 8.7.37 Release

The Espresso release for AP2 version 8.7.37 includes feature enhancements to the Enhanced Service Investigator, Dashboards, Device Investigator, Device Investigator Layouts , and the Events page, including improvements to the Timeline panel, the addition of the Device Dashboards page, and a new text editor on the Event Policy Editor page.

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, 12.2.1, or 12.2.0 before installing AP2 Espresso.

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 Espresso update must be administered to systems that host AP2. All SL1 systems must be on the same AP2 version.

Installing or Uninstalling AP2 Espresso

To install AP2 Espresso version 8.7.37:

  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 Oracle Linux 8 (OL8) release, or the 12.2.1 Oracle Linux 8 (OL8) release. For more information, about upgrading to those releases, see the appropriate SL1 platform release notes. 
    • If you are installing AP2 Espresso version 8.7.37 on SL1 version 12.1.1, proceed to step 2.
    • If you are installing AP2 Espresso version 8.7.37 on SL1 12.2.0 or 12.2.1, you can skip to step 5.
    • If you have already installed the libem7 RPM file from the ScienceLogic Support site, proceed to step 5.

    The AP2 Espresso RPM file does not support Aurora3 in an AWS environment.

  2. If you are installing AP2 Espresso on SL1 version 12.1.1, 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 Espresso RPM file locally from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL0000000C1B0AU/espresso
  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-<espresso-release-ap2-version>.rpm em7admin@<system-ip-address>:/home/em7admin/

    where:

    • aws-system-pem is the PEM file for the AWS system.
    • espresso-release-ap2-version is the AP2 Espresso 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-<espresso-release-ap2-version>.rpm

    where espresso-release-ap2-version is the AP2 Espresso release version.

  9. Enter y to confirm the installation of the AP2 RPM file.
  10. If you have not installed the libem7 file and are installing it for the first time, proceed to step 11. Otherwise, skip to step 13.
  11. Install the libem7 RPM file on your system by running the following command:

    12. sudo yum install libem7-ipcserver-0.2.0-1.el8.x86_64.rpm

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

    14. sudo systemctl enable libem7.socket

    sudo systemctl start libem7

    sudo systemctl daemon-reload

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

    15. sudo systemctl restart nextui.service

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

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

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

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

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

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

    20. sudo dnf repolist

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

    21. sudo dnf module list --all nodejs

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

    22. sudo dnf module enable nodejs:18

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

    23. sudo dnf module install nodejs

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

    24. which node

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

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

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

    26. sudo systemctl daemon-reload

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

    27. sudo systemctl restart nextui.service

To uninstall the Espresso release features for AP2 version 8.7.37:

  1. If you are uninstalling AP2 Espresso version 8.7.37 from SL1 version 12.1.1, proceed to step 2. If you are uninstalling AP2 Espresso version 8.7.37 from SL1 12.2.0, you can skip to step 5. If you are uninstalling AP2 Espresso version 8.7.37 from SL1 version 12.2.1, proceed to step 8.

    2. The AP2 Espresso RPM file does not support Aurora3 in an AWS environment.

  2. If you are uninstalling AP2 Espresso 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 Espresso version.
    • system-ip-address is the IP address of your SL1 system.
  5. If you are uninstalling AP2 Espresso on SL1 version 12.2.0, you must download the AP2 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 Espresso version.
    • system-ip-address is the IP address of your SL1 system.

  8. If you are uninstalling AP2 Espresso on SL1 version 12.2.1, you must download the AP2 Doughnut RPM file locally to your machine from the ScienceLogic Support site: https://support.sciencelogic.com/s/release-file/aBtVL00000008nB0AQ/doughnut

  9. Either go to the console of the SL1 Database Server or use SSH to access the Database Server.

  10. At the shell prompt, copy the RPM file to the AWS system by running the following command:

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

    12. sudo rpm -U --force --replacefiles nextui-<rollback-ap2-version>.rpm

    where rollback-ap2-version is the rollback AP2 version.

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

    13. sudo systemctl disable libem7.socket

    sudo systemctl stop libem7

    sudo systemctl deamon-reload

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

    sudo systemctl restart nextui.service

Important Upgrade Notes for AP2 Espresso 8.7.37

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 Espresso version 8.7.37

This section describes the features and enhancements that are included in SL1 AP2 Espresso version 8.7.37.

Business Services

  • What's new: Improved Enhanced Service Investigator page. The Timeline panel on the enhanced Service Investigator page now shows the health, availability, and risk statuses of your events in the last 7 days by default. (Jira ID: SLUI-19215) 
  • What's new: Updated default Business Services policy. Device availability reflects the active status of constituent devices for physical and component devices. (Jira ID: SLUI-19247)  

    The following updates were made to support this enhancement:

    • Replaced availability vital metrics and the "All Devices" filter with "isActive=True".
    • Replaced the aggregation type of "Availability" with "Count".
    • Set the rule to "Available" if at least a device has the "IsActive=True" filter.
    • Updated the default aggregation factor for IT, Business, and Services Model service policies from "Average" to "Minimum".
  • For more information: See the section on Using the Enhanced Service Investigator in the Business Services manual.

Dashboards

  • What's new: Added navigation to the Device Dashboards page in the classic SL1 user interface. You can now go to the Device Dashboards page (System > Custom > Device Dashboards). This link redirects you to the Device Dashboards page in the SL1 Classic user interface. (Jira ID: SLUI-19318)
  • What's new: Improved Dashboards page and widgets . Removed the 50 return limit for Interface widgets with the Table visualization and added infinite scroll. (Jira ID: SLUI-17340)

    • Interface widgets with Table visualizations now displays information in the footer, such as the total, selected, and filtered counts. (Jira ID: SLUI-17340)

Additional Dashboards Updates

  • Updated and organized information in the footer of tables, such as the total, selected, and filtered counts. (Jira ID: SLUI-17340)

Devices

  • What's new: Device Investigator Layouts management optimization. You can now edit Device Investigator layouts, copy and save existing layouts with different names. (Jira ID: SLUI-19285)
  • For more information: See the section on Using the Device Investigator in the Managing Devices manual.

Additional Devices Updates

  • Added a "deviceGroup" search parameter to the "relatedNodes" query to support the upcoming Relationships widget in the Device Investigator. (Jira ID: SLUI-19371)
  • Updated the method for performing bulk actions to multiple devices on the Devices page. Previously, you could select from several action-specific icons at the top of the page. With this update, those icons have been replaced by an Actions drop-down menu that includes a list of available bulk actions. In addition, that drop-down menu now includes a new Schedule Maintenance option for scheduling maintenance events on multiple selected devices. (Jira ID: SLUI-19094)

Events

  • What's new: Added Table Preferences menu to the Events page. The new Table Preferences menu is now available from the Grid Settings menu. The Table Preferences menu includes the following toggles: (Jira ID: SLUI-18694)

    • Background Fill

    • Masked Events

  • What's new: New text editor for Event Policy Editor. Replaced the text editor on the Event Policy Editor page with a FROALA editor. (Jira ID: SLUI-19492)

    • A FROALA editor is a front-end HTML editor for enabling text editing capabilities for web application, software, etc..

Additional Events Updates

  • Removed the "experimental" labels from several GraphQL resources and are now standard fields. (Jira ID: SLUI-18747)
  • Updated the error messages in the Suppression tab on the Event Policies page for policies with invalid device IDs. (Jira ID: SLUI-19395)

Additional New Features and Enhancements for Espresso

Devices

  • When adding devices using the guided discovery process from the Discovery Sessions page (Devices > Discovery Sessions), devices for which your SL1 system does not have the required entities will now appear in a secondary section at the bottom with a new warning note. This note will specify why you cannot add the selected device and the necessary prerequisites. (Jira ID: SLUI-19587)

GraphQL

  • When you run a GraphQL query for an "Appliance" type, you will also get the current operating system version for that appliance. (Jira ID: SLUI-19542)
  • Added a "powerpackid" field to the "guidedDiscoveryWorkflow(s) GraphQL queries (read-only, searchable). This field displays the PowerPack ID. If the guided discovery workflow contains a reference to a PowerPack that is not installed on the system, it will return a placeholder object with its "powerpackId", and "name" which will display as "N/A", and the "id" as "-1". (Jira ID: SLUI-19312)

Known Issues

The following known issues affect version 8.7.37 of the AP2 Espresso 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 deleting a device from the Devices page from the Actions menu (), the Delete Devices modal displays for an indefinite period of time. (Jira ID: SLUI-19738)

    • The current solution to this issue is to select the checkbox next to the device(s) you want to delete, click Delete Devices to open the Delete Devices modal, then click Delete.

  • 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

    }

    }