SL1 AP2 Croissant version 8.5.7 Release

The Croissant release for AP2 version 8.5.7 includes feature enhancements to the Device Investigator, Events, and Dashboards pages, new ways to manage your business services, and GraphQL updates to support the enhancements to Device Investigator layouts.

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 Croissant.

For details on upgrading SL1, see the appropriate SL1 platform release notes.

This update is available only to cloud-based (SaaS) SL1 systems. The AP2 Croissant update must be administered to systems that host AP2. All SL1 systems must be on the same AP2 version.

Installing or Uninstalling AP2 Croissant

You can find all AP2-related files on AP2 Release Versions page of the ScienceLogic Support site (SL1 Product Downloads > SL1 Platform > AP2 Releases).

To install AP2 Croissant version 8.5.7:

  1. If you have not already done so, upgrade your SL1 system to either the 12.1.1 Oracle Linux 8 (OL8) release or the 12.2.0 release. For more information, about upgrading to those releases, see the appropriate SL1 platform release notes.
    • If you are installing AP2 Croissant version 8.5.7 on SL1 version 12.1.1, proceed to step 2.
    • If you are installing AP2 Croissant version 8.5.7 on SL1 12.2.0, you can skip to step 5.
  2. If you are installing AP2 Croissant on SL1 version 12.1.1, 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 Croissant RPM file locally from the ScienceLogic Supportsite: https://support.sciencelogic.com/s/release-file/aBtVL00000002530AA/croissant
  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-<croissant-release-ap2-version>.rpm em7admin@<system-ip-address>:/home/em7admin/

    where:

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

    where croissant-release-ap2-version is the AP2 Croissant 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 Croissant version 8.5.7 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.5.7.

To uninstall the Croissant release features for AP2 version 8.5.7:

  1. If you are uninstalling AP2 Croissant version 8.5.7 from SL1 version 12.1.1, proceed to step 2. If you are uninstalling AP2 Croissant version 8.5.7 from SL1 12.2.0, you can skip to step 5.
  2. If you are uninstalling AP2 Croissant 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 Croissant 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 Biscotti 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 daemon-reload

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

    sudo systemctl restart nextui.service

Important Upgrade Notes for AP2 Croissant 8.5.7

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 Croissant version 8.5.7

This section describes the features and enhancements that are included in SL1 AP2 Croissant version 8.5.7.

Dashboards

  • What's new: Added new Custom widget . Added a new Custom widget on the Create Widget page. This widget provides a user-interface-only visualization, and allows you to select the type of visualization you want to use under the Visualizations drop-down field. The title of your Custom widget will correspond to the name of the visualization option you have selected. The Custom widget currently only has the new HTML Widget visualization option. This visualization allows you to preview the widget on the right-hand side of Create Widget page, and then also make changes through the newly added text editor component. The following additional changes were made to support this new feature:   

    • View or edit HTML content directly in the text editor, either in the Basic tab, which allows you to update the widget by editing plain text directly, or the Advanced tab, which allows you to view and edit the raw, HTML content.

    • Custom widgets that are using the HTML Widget visualization, can render any rich content or HTML that you input. To do so, click the Advanced tab, which subsequently opens the code view by default. Alternatively, you can click the ellipses button () on the top-right corner of the Preview pane, then select Code View ().

Additional Dashboards Updates

  • Added a new Last 2 days option to the Time span filter drop-down field on the Dashboards page.

  • You can now integrate third-party tools into SL1 with external linking. To do so, toggle on Items link to another page when creating widgets. When you do so, two additional fields will appear, Link base URL and Link Tooltip. This new feature supports the following widgets and their corresponding visualization options:

    • Device widgets that have Leaderboard or Table visualizations.

    • Interface widgets that have Leaderboard or Table visualizations.

Devices

  • What's new: The Relationships widget. Added a new Relationships widget to the Device Investigator that displays details about the other devices and services that have relationships to the selected device. The Relationships widget, which appears in the Device Investigator by default, includes the following columns:

    • Health, which displays the current condition of the related device or service, based upon events generated by the device or service.

    • Name, which displays the name of the related device or service. You can click the name to view the investigator page for that device or service.

    • Relationship, which indicates the type of relationship the device or service has with the selected device. You can filter the list of devices and services that appear in the widget by selecting one or more relationship types from this drop-down field.

    • Type, which indicates whether the relationship is a device or a service.

  • What's new: Custom Device Investigator layouts and alignments. Added the ability to view details about custom Device Investigator layouts, as well as the ability to bulk align layouts that you own to specific device categories, device classes, and devices.

    Layouts and layout alignments can be private, which are owned by a specific user, or public, which are available to everyone.

    The following updates were made to support this enhancement:

    • Added a Choose Layout tab when you click the Edit (layout) button from the Device Investigator. This tab includes a list of existing Device Investigator layouts that you own or have access to. You can change the Device Investigator layout that is currently aligned to that device by clicking the radio button for a different layout.

    • Added a new Device Investigator Layouts page (Devices > Device Investigator Layouts), where you can view a list of the existing Device Investigator layouts that you own or have access to. You can also access this page from within the Device Investigator by clicking Edit (layout) > Choose Layout > Manage Layouts. This page includes the following information about each layout:

      • Layout name, ID, and owner

      • The number of device categories, device classes, and devices aligned to each layout

      • The date and time the layout was last edited, as well as the user responsible

      To view this page, you must have an Administrator user account type with an access key that includes the DEV_VIEW access hook aligned to your user account.

    • From the Device Investigator Layouts page, you can click the Layout Name link for a particular layout to view or filter the list of specific device categories, device classes, and devices that are aligned to that layout. If you are the layout owner, you can also edit the layout name or its alignments.

Additional Devices Updates

  • Added a new ID column to the Collections tab of the Device Investigator that displays the ID number of each Dynamic Application listed on the page.

  • Updated the table that appears on the Events tab of the Device Investigator. As part of this update, the following changes were made:

    • The ID column is now labeled Event ID.

    • Columns were added for Masked Events and Automated Actions.

Events

  • What's new: The Masked Events modal. Added a new Masked Events modal that you can access from the Events page. On the Events page, any event that contains masked events includes an icon () that you can click under the Masked Events column. You can click this icon to open the new Masked Events modal.

    • The following updates were made to support this enhancement:

    • The Masked Events modal displays the same events table from the Masked Events widget on the Event Investigator page. This modal also contains an event overview, which you can still access from the Event Overview widget on the Event Investigator page. You can perform all the same functions in this modal as you would be able to in the Masked Events widget, and the Event Overview widget on the Event Investigator page.

    • You can access the Masked Events modal in SL1 global manager for business services.

Additional Events Updates

  • You can now add color-coded highlights to rows on the events inventory table that correspond to the severity color of the event. To do so, go to the Events page, click the View drop-down field, then switch the toggle on for Highlight rows by severity option.
  • You can now perform a bulk action for editing event notes on the Events page.

Additional New Features and Enhancements for Croissant

Business Services

  • When creating status policies for your business services, Percent will now appear under the Aggregate drop-down field. For instance, if one or more devices in your service are unavailable, SL1 will display the number of unavailable devices as a percentage of the total number of devices for that particular service.
  • The following inventory pages and tabs in the SL1 user interface have been updated to use a new set of filters for the columns in the list. You can start typing filter text or select filter options in one or more of these filters to narrow down the list to just the items you want to view:

    • Service Templates page (Business Services > Templates)

    • Policy Editor page (Enhances Service Investigator > Status Policy)

    • Maps page (The Maps tab on the left-side navigation menu)

    • Maps window (Maps > Create Maps)

    • Add Node window (Maps > Add Node)

GraphQL

  • 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.
  • Made the following GraphQL updates to support the enhancements to Device Investigator layouts:

    • Added an alignedDeviceInvestigatorLayouts field to the device, deviceClass, and deviceCategory objects.

    • Enhanced DeviceSearch, DeviceClassSearch, and DeviceCategorySearch with a new alignedDeviceInvestigatorLayout field.

    • Added a new deviceInvestigatorLayoutAlignment node that includes fields such as id, parentType, parentId, user, layoutId, editedBy, and editedDate.

  • To support the new Relationships widget for the Device Investigator, added a new DeviceInvestigatorLayoutRelationshipInput field that can be included in layout arguments for the createDeviceInvestigatorLayout and updateDeviceInvestigatorLayout mutations.
  • Added a new statistics category to the aiMachineLearningMetricAnomalies node to improve the performance of AI/ML prediction metric GQL queries. This category includes two new fields, anomalyCount and maxAnomalyScore, which are calculated over a provided timeSpan input.
  • Added a LinkedMetric GraphQL node for events.

User Interface

  • Added a new Density setting to the gear icon and ellipses drop-down field that appear at the top of all inventory pages. This setting enables you to switch between two settings:

    • Compact, which uses less padding between rows and a smaller font size.

    • Comfortable, which uses more padding between rows and a larger font size.

Issues Addressed in SL1 AP2 Croissant version 8.5.7

This section describes the issues that were addressed in SL1 AP2 Croissant version 8.5.7.

Authentication

  • Made updates to ensure that, if you are on a specific page in SL1 and have to log back in using the single sign-on login page, SL1 returns you to the page you had previously been on rather than your default landing page. (Cases: 00291753, 00415130)

Business Services

  • Resolved an issue where the Health, Availability, and Risk field values were displaying as "Unknown" due to gaps in the data sets across business services, and timeouts in GraphQL requests. (Case: 00382593)

Dashboards

  • Addressed an issue where Device widgets with Table visualizations on the Dashboards page for the "Cisco: Meraki [API]" PowerPack was not displaying data. (Case: 00396156)
  • Addressed an issue where log files from the SL1 Developer Logs page (System > Tools > SL1 Developer Logs) did not include debug logs in the report. (Case: 00353242)

Known Issues

The following known issues affect version 8.5.7 of the AP2 Croissant release:

  • Organizations must have at least one or more accounts assigned to them to ensure the relevant services are saved.
  • Services that are added or created to the N-tier hierarchy have their RCA Options field set to Disabled by default.

    • 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.

    • Before deleting child services in a 3-tier hierarchy, check if the parent service has the RCA Options field Enabled, then set this field to Disabled if it is not already.

  • 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":

    • mutation updateMaxValue{

    updateFeatureToggle(id: "system:BUSINESS_SERVICES_MAX_POLICIES", value: "<increased value>") {

    id

    value

    }

    }