Skylar One (SL1) 12.3.16 Release Notes

ScienceLogic strongly recommends that you review the installation and upgrade instructions, important upgrade notes, and known issues for this release before installing or upgrading to Skylar One 12.3.16.

The Skylar One (SL1) 12.3.16 release updates the default AP2 version to 9.13.1-14 (Quesito), adding the new features, enhancements, and addressed issues from AP2 version 8.17.23-45 (Ice Pop) through Quesito. It also addresses issues in the system upgrade and deployment process, and resolves several known security vulnerabilities.

These release notes provide a comprehensive list of the features, enhancements, and addressed issues that are included in the Skylar One 12.3.16 release.

To view the updates that are included in previous Skylar One releases, see the following release notes:

Some of the features, enhancements, and addressed issues that are included in this Skylar One release were originally included in the following Skylar One AP2 releases:

AP2 version 9.13.1-14 (Quesito) is installed by default in Skylar One 12.3.16.

Before You Proceed

If you are planning to consume Skylar One 12.3.16, be advised of the following:

  • The 12.3.16 release is available only as a patch.

  • The validated upgrade paths to version 12.3.16 are outlined below. Be advised that you can perform upgrades from one minor version to any later minor version within the 12.3.x series. However, as with all updates, ScienceLogic strongly recommends that you perform such upgrades in a test environment before implementing the upgrades in production environments.

    The following are the validated upgrade paths:

    • 12.3.15 > 12.3.16

    • 12.3.11 > 12.3.16

    • 12.3.7 > 12.3.16

    • 12.2.7 > 12.3.16 (be advised there is a known issue that affects this upgrade path)

  • Version 12.3.16 requires you to upgrade MariaDB to 10.6.28.

  • 12.2.x and 12.3.x STIG-compliant users can upgrade to this release via one of the supported upgrade paths so long as you have not consumed or upgraded to the 12.3.0 STIG release. If you previously deployed or upgraded to 12.3.0 STIG, you cannot upgrade to 12.3.16 STIG due to a known technical issue. If this scenario impacts you, contact your ScienceLogic account manager for more details.

  • If you are on an 11.x MUD system, you cannot upgrade directly to this release; you must first follow the approved conversion process from 11.x MUD to 12.2.1.1 STIG and then upgrade to 12.3.16 STIG. For more information, see the section on STIG Support.

  • AWS deployments that are using Aurora 3 can upgrade to this release. If you are currently deployed using Aurora 2, you can upgrade to this release, but you must perform a post-upgrade Aurora 2 to 3 conversion.

  • There is a known issue that might cause the upgrade to 12.3.16 to fail during post-update with a "Database Synchronization failed after 3 attempts" error in both the UI logs and the /var/log/em7/patch_manager.log file. For more information about this issue, including a pre-upgrade script you can run to avoid it, see https://support.sciencelogic.com/s/article/21802.

  • Skylar One 12.3.15 added a new, post-update cleanup script that removes old patch bundles to free space on the Database Server. This cleanup process can increase upgrade time during the first run, especially on systems with a large number of older patch bundles. To reduce upgrade time, you can pre-clean older patches before upgrading.

  • Skylar One 12.3.16 is Department of Defense Information Network (DoDIN)-certified.

For more information, see the Important Upgrade Notes and Known Issues sections.

New Features and Enhancements in Skylar One 12.3.16

This section describes the new features and enhancements that are included in Skylar One 12.3.16.

Business Services

  • Improved the process for creating and editing service policy rules on the Service Investigator page:

    • You can choose the metric, aggregation method, and timespan for each rule, and the preview graph uses raw, hourly, or daily summarized data based on the selected timespan.

    • You can insert new conditions into any rule and set specific thresholds that trigger alert messages when crossed.

  • Renamed the RCA Options column and field to Service Analysis on the Business Services page and in the Overview panel of the Service Investigator page.

  • You can now update the refresh interval for services in bulk on the Business Services page. To do so, select the checkboxes next to the services you want to update, then select Update Refresh Interval from the Actions field.

  • Made several updates to the Timeline panel of the Service Investigator page:

    • The panel now includes an Anomalies row that displays events marked as anomalies over time.

    • Skylar AI event icons display in the color that matches their event severity.

    • The Skylar AI and Changes sections automatically expand or collapse based on whether relevant events exist in the selected time range. You can also expand or collapse them manually.

    • The total number of events now appears in parentheses next to each swim lane title, and the swim lane headers use adjusted text size and divider lines for clearer visual distinction between sections.

    • The maximum time range viewable in this panel has been extended from 12 hours to 24 hours.

  • Added a new Service Insights page (Business Services > Service Insights) that provides key metrics and visualizations on service adoption, processing statistics, and top services by recalculation time.

    The page includes the following:

    • An information bar showing an overview of all services, including total, root, aggregate, device, shared, disabled, empty, and orphaned services.

    • Line graph widgets showing hierarchy calculation and HAR refresh times.

    • Bar chart widgets highlighting the top services by constituent count and HAR calculation time.

    • Widgets listing services with zero constituents and orphaned services.

  • The Overview panel on the Service Investigator page now includes a Location field showing the geographic location aligned to the service, and you can assign a geographic location to a service when saving it from the Service Investigator. The assigned location is used to align the service with geographic maps.

  • The Classic IT Services menu option in the default Skylar One user interface (AP2) will be removed in a future release. It remains fully functional and accessible until then.

Dashboards

  • Added a new Web Content widget type for dashboards, which lets you visualize web content monitoring data such as connection time, lookup time, download speed, and page size.

    • When creating this widget, you can select from three metric types: Device Properties, Web Content Monitors, and Monitoring Policy Properties.

    • The widget supports Line Chart, Number, and Table visualizations.

    • You can filter and select specific monitoring policies, set rollup frequency and aggregation options per metric, and choose a unit prefix to control how metric values display.

Devices

  • Added new device actions to the Devices page.

    • A new drop-down arrow button next to the Add Devices button provides additional device actions, including creating a physical or virtual device, creating a physical device from a file, installing an agent, and merging or unmerging physical and component device records that represent the same device.

    • From the Actions button, you can now create an asset record, align the Device Investigator layout, and create reports for one or more selected devices.

  • Added the following new columns to the Devices page:

    • SL Agent, which indicates whether an Skylar One (SL1) agent is installed on the device.

    • SNMP Credential and SNMP Version, which display the SNMP credential and version used to monitor the device.

    • Filterable columns for any custom attributes you have defined for your devices, including extended custom attributes.

  • Added enhanced topology configuration options at the device level. Four new fields on the Settings tab of the Device Investigator page let you configure enhanced Layer-2, Layer-3, Cisco Discovery Protocol (CDP), and Link Layer Discovery Protocol (LLDP) processing for individual devices. This enhancement provides additional context about device relationships, better topology maps, and improved event correlation.

  • Added a new Location Name field to the device Info drawer on the Device Investigator page to support location mapping for geographic maps.

Events

  • Redesigned the Event Policy Editor page, reorganizing it into three tabs:

    • Basic, for the fundamental requirements of an event policy.

    • Advanced, for topology masking, device sub-entity settings, and external system integration.

    • Summary, which provides an at-a-glance view of the event policy and its linked alert.

  • You can now align event policies to specific organizations rather than leaving them "Global" by default.

  • Replaced the classic, iframed Event Suppressions page (Events > Suppressions) with a version designed specifically for the default Skylar One user interface (AP2):

    • You can view and unsuppress events directly, including device or device group name, IP address, event policy details, severity, and creation metadata.

    • You can delete individual or multiple event suppressions.

    • You can filter the table by column.

  • Replaced the classic, iframed Event Category Manager page with an Event Categories page (Events > Event Categories) designed specifically for the default Skylar One user interface (AP2). This new page lets you view, create, edit, and delete event categories from a sortable, filterable table.

  • Added column filtering for base and extended custom attributes to the table on the Events page and to events-related dashboard widgets.

Global Manager

  • Improved Global Manager request performance with a new stack cache, which is enabled by default. You can configure the cache time-to-live, or disable the cache, using the system configuration settings.

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

Maps

  • Added a new Geographic Maps page (Maps > Geographic Maps) that lets you create and manage custom geographic maps to visualize devices or business services on a map and provide location-based insights at a glance.

    You can manage device and service location data in either of the following ways:

    • Upload the data in bulk.

    • Manage it directly in the user interface from a new Locations page (Manage > Locations), which lets you add, edit, and delete locations and align or un-align devices and services with them.

  • Improved geographic map performance, detail, and scaling: maps now load faster, display more detailed terrain and boundaries by default (including worldwide state-level boundaries and labels), and scale more reliably for maps with large numbers of nodes.

Platform and Security

  • Skylar One version 12.3.16 includes package updates to improve security and system performance. This includes updates to address the following known vulnerabilities: CVE-2026-999999, CVE-2026-114406, CVE-2026-111497, CVE-2026-109619, CVE-2026-109618, CVE-2026-107823, CVE-2026-107821, CVE-2026-107818, CVE-2026-107815, CVE-2026-107814, CVE-2026-88044, CVE-2026-88018, CVE-2026-88017, CVE-2021-29489, CVE-2018-20801.

  • Skylar One version 12.3.16 requires you to upgrade MariaDB to 10.6.28.

Skylar AI

  • Improved the workflow for enabling and disabling anomaly detection alerting on the Anomaly Detection page:

    • Clicking the Enable Alert Policies button now opens a modal that lets you select devices, Dynamic Application metrics, and indexes on which to enable alerting.

    • Enabling or disabling a metric now updates its alerting state while keeping the metric visible.

  • Updated how the Skylar AI Insights count is calculated on the Device Investigator page. The value now reflects the sum of all open root cause analysis events, open anomaly index score events, and open predictive alert events, and is hidden entirely if the system is not connected to Skylar AI.

  • Added two new columns to the Anomaly Detection page:

    • Device Anomaly Count, which displays the total number of metrics with anomalies on the selected device.

    • Metric Anomaly Count, which displays the number of anomalies for the selected metric.

System Update

  • Implemented a new "Patcher Task Manager" service (siloupdate-taskman) that replaces the siloupdate-spool service, which is no longer required for system update. (Jira ID: EM-78246)

  • Updated the 35_db_compute-data_update.sh script to ensure that database update failures are no longer silently masked. (Jira ID: EM-78700)

Issues Addressed in Skylar One 12.3.16

This section describes the issues that were addressed in Skylar One 12.3.16.

Agents

  • Resolved an issue that prevented the Agents page from being accessed or displayed in some environments. (Cases: 00573304, 00586748, 00552775, 00564899) (Jira ID: SLUI-23209)

API

  • Resolved an issue where Run-As accounts could be granted incorrect access hooks. (Jira ID: SLUI-21770)

  • Resolved an issue with Aurora 3 where you were unable to enable TLS verification through the user interface or the API. (Jira ID: SLS-1500)

Business Services

  • Resolved an issue where the sunburst chart in the Overview panel of the Service Investigator page did not load for certain device services. (Jira ID: SLUI-21084)

  • Resolved an issue where services deleted prior to the AP2 Lokma release were still appearing in the database despite their removal. (Jira ID: SLUI-21757)

  • Resolved an issue where severity chips for healthy events were not displaying for cleared Skylar AI events in the Skylar AI section of the Timeline panel on the Service Investigator page. (Jira ID: SLUI-22256)

  • Resolved an issue where editing different service policy rules that use the same Dynamic Application but different metrics displayed the wrong metric label on the Y-axis of the preview graph. (Case: 00562795) (Jira ID: SLUI-23118)

  • Resolved an issue where, for services with the Service Analysis 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 five minutes by default. (Jira ID: SLUI-18853)

  • Resolved an issue that caused the Business Services page to display an error page after upgrading Skylar One to version 12.3.9. (Case: 00593376) (Jira ID: SLUI-23194)

  • Resolved an issue that prevented HTTP headers from being added to custom universal credentials. (Case: 00603323) (Jira ID: SLUI-23493)

  • Resolved an issue where the Service Name field on the Create Service from Template page was not editable until an organization was selected. (Jira ID: SLUI-23099)

Credentials

  • Resolved an issue where the Select Credential Test field in the Credential Tester panel of the Edit Credential modal did not show the full list of credential tests. (Case: 00517459) (Jira ID: SLUI-22132)

  • Resolved an issue where the Create Credential modal for an AWS credential incorrectly displayed the Enable FIPS Endpoint and Enable SSL Verification toggles. (Case: 00523734) (Jira ID: SOL-29705)

  • Resolved an issue where the Credentials page occasionally did not load or display all credentials. (Case: 00551140) (Jira ID: SLUI-22673)

  • Resolved an issue where the Select Credential Test field displayed tests that did not apply to the selected credential type; this field now shows only the credential tests relevant to that type. (Case: 00526225) (Jira ID: SLUI-22371)

  • Resolved an issue where adding or updating SSH credentials with a valid Privacy Enhanced Mail (PEM) key did not save the change. (Jira ID: SLUI-23324)

  • Resolved an issue where the Create Credential modal did not display guidance text for certain credential types. (Jira ID: SLUI-23265)

  • Resolved an issue where editing a credential and changing its organization visibility setting overwrote the credential's password with invalid data, even when the password field was not changed. (Case: 00596045) (Jira ID: SLUI-23562)

Dashboards

  • Resolved an issue that occurred when creating a Grouped Data Series (Leaderboard/Top-N secondary data) widget. (Jira ID: EM-80574)

  • Resolved an issue where the Dashboards page malfunctioned when typing too quickly in a widget's search field. (Case: 00496272) (Jira ID: SLUI-21561)

  • Resolved an issue where the Subscription Usage page previewed only a limited number of devices instead of the full list of device license usage. (Case: 00424541) (Jira ID: SLUI-19903)

  • Filesystem and Services widgets that are subscribed to other widgets no longer retain the publishing widget's data after all rows in the publishing widget have been deselected. (Jira ID: SLUI-21548)

  • Resolved an issue where the Filter (X) button generated an error when narrowing down widget data using a basic query on name. (Jira ID: SLUI-21132)

  • Resolved an issue where the Subscription License Reports widget inaccurately reported licenses when multiple instances of the Dashboards page were open at the same time. (Jira ID: SLUI-20951)

  • Resolved an issue that caused multiple GraphQL errors when loading a dashboard that has File Systems widgets over 1 TB. (Case: 00489856) (Jira ID: SLUI-21218)

  • Resolved an issue where radio buttons malfunctioned for Devices widgets using the Leaderboard visualization option. (Case: 00489835) (Jira ID: SLUI-21554)

  • Resolved an issue where performance metric references in dashboard widgets could display incorrect or blank values when the dashboard was installed through a PowerPack. (Case: 00494949) (Jira IDs: SLUI-21486, SLUI-22044)

  • Resolved an issue where auto-refreshing on the Dashboards page did not keep user sessions active, even when the Page Auto-Refresh Keeps User Session Active field was set to Enabled on the Behavior Settings page. (Case: 00503563) (Jira ID: SLUI-21787)

  • Resolved an issue where the Total Network Traffic widget on the default Server dashboard displayed errors instead of data. (Case: 00516146) (Jira IDs: SLUI-22206, SLUI-21831)

  • Resolved an issue where Device widgets using the Line Chart visualization could not be saved when a negative value was entered in the Threshold Line field. (Case: 00488189) (Jira ID: SLUI-22119)

  • Resolved an issue where selecting multiple devices for widgets using the Forecast visualization did not display information for all selected devices. (Case: 00526493) (Jira ID: SLUI-22344)

  • Resolved an issue where File System widgets using the Line Chart visualization sometimes displayed default data labels in the chart legend instead of the correct file system labels. (Case: 00498710) (Jira ID: SLUI-21890)

  • Resolved an issue where widgets using the Table or Bar Chart visualizations on the Dashboards page did not update when the time span was adjusted. (Case: 00515942) (Jira ID: SLUI-22260)

  • Resolved an issue where Interfaces widgets using the Heat type did not display the heat map after saving. (Case: 00552693) (Jira ID: SLUI-22686)

  • Resolved an issue where editing and saving the Collection State column in Interfaces widgets could cause widget data to disappear. (Jira ID: SLUI-22777)

  • Resolved an issue where a dashboard shared by an administrator lost its shared organization settings if a non-administrator user edited and saved it. (Jira ID: SLUI-22691)

  • Resolved an issue where toggling on This widget can drive other widgets in a Device widget using the Table visualization caused selected checkboxes to blink in the Preview pane. (Jira ID: SLUI-22678)

  • Resolved an issue where dashboards could not be shared with organizations other than "System" using the Visibility column in Global Manager. (Jira ID: SLUI-22669)

  • Resolved an issue where the Scale Prefix field appeared twice when adding metrics and properties to a widget. (Jira ID: SLUI-22508)

  • Resolved an issue where devices did not appear as expected in dashboard widgets and filters. (Jira ID: SLUI-22960)

  • Resolved an issue where the Dashboards page did not remain stable when displaying dashboards with a high number of widgets using chart visualizations, regardless of the selected date and time range. (Case: 00519023) (Jira ID: SLUI-22480)

  • Resolved an issue that prevented custom attribute columns in Events widgets using the Table visualization from being resized or reordered using drag-and-drop. (Jira ID: SLUI-23233)

  • Resolved an issue where dashboard widgets could display an error when filtering interfaces by more than one tag. (Case: 00598090) (Jira ID: SLUI-23313)

  • Resolved an issue where, in a Devices or File Systems widget using the Number visualization, toggling off Show the Unit left the Show the Prefix toggle visible but nonfunctional. (Jira ID: SLUI-23147)

  • Resolved an issue where toggling Show the Metric on or off when creating a Devices widget using the Number visualization did not update the Preview pane if CPU metrics were added after selecting Vitals. (Jira ID: SLUI-23685)

  • Resolved an issue where GraphQL queries for the Web Content widget did not return the expected metric values when filtering using less-than or greater-than comparisons. (Jira ID: SLUI-23256)

  • Resolved an issue where widgets using the Leaderboard Bar Chart visualization briefly displayed the correct data before the bars dropped to zero, even though hovering over the bars still showed the correct values. (Case: 00634016) (Jira ID: SLUI-23714)

Data Collection and Retention

  • Reduced database load caused by API requests for interface data by optimizing the underlying query. (Case: 00639899) (Jira ID: EM-79914)

Devices

  • Resolved an issue where bulk action options under the Actions button on the Devices page were not sorted alphabetically in the Firefox browser. (Jira ID: SLUI-20870)

  • Resolved an issue where the Relationships and Memberships widget on the Device Investigator page could not properly display the table of services on the Services tab. (Jira ID: SLUI-20564)

  • Resolved an issue that prevented columns from being hidden when the table on the Devices page was sorted or filtered by those columns. (Jira ID: SLUI-20413)

  • Resolved an issue where cleared Skylar AI events did not appear on the Events tab of the Devices page when sorting the table by cleared events. (Jira ID: SLUI-20889)

  • Resolved an issue that caused a "Float cannot represent non numeric value: Infinity" error when accessing the Skylar One (SL1) console after creating or editing device services. (Jira ID: SLUI-21002)

  • Resolved an issue that prevented users from duplicating or assigning icons to device categories on the Device Categories page. (Jira ID: SLUI-21016)

  • Resolved an issue where the Collector Groups page displayed an incorrect maximum of 10 Data Collectors per collector group instead of the correct number. (Case: 00501726) (Jira ID: SLUI-21874)

  • Resolved an issue where searching for the location of an asset or device on the Asset Manager page resulted in an error. (Case: 00500159) (Jira ID: SLUI-21765)

  • Resolved an issue that caused a search on collectionState in the "getInterfaces" GraphQL query to return an error. (Case: 00523713) (Jira ID: SLUI-22466)

  • Resolved an issue that prevented the columns on the Events tab of the Device Investigator page from being sortable. (Jira ID: SLUI-20991)

  • Resolved 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 Device Investigator page by adding visual dividers and updated tooltips, so that the top chart shows only anomaly scores and the bottom chart shows metric values and expected ranges with units. (Jira ID: SLUI-22379)

  • Resolved an issue where the Anomaly Detection tab appeared on the Device Investigator page even when the device was not collecting data for Skylar Analytics. (Jira ID: SLUI-23144)

  • Resolved an issue where you could assign the same value to different devices for a newly created base custom attribute marked as unique. (Jira ID: SLUI-23430)

  • Resolved an issue where initiating maintenance mode on a device did not record that action in the device log. (Case: 00446506) (Jira ID: SLUI-23664)

  • Resolved an issue that prevented columns on the Devices page from being resized or reordered. (Jira ID: SLUI-20081)

  • Resolved an issue on the Device Investigator page where sorting by the number of devices, device classes, and device categories did not work as intended. (Jira ID: SLUI-18855)

  • Resolved an issue that prevented the list of collector groups from scrolling in the Change Collector Group modal. (Jira ID: SLUI-22980)

  • Resolved an issue where newly created indexed base custom attributes automatically appeared as default columns on the Devices page. (Jira ID: SLUI-23663)

  • Resolved an issue where ampersand (&) characters in organization names did not display correctly. (Jira ID: SLUI-23463)

  • Resolved an issue where the Devices page did not work as intended when filtering the Collector Groups column with multiple group names. (Jira ID: SLUI-21035)

  • Resolved an issue where the Help button on the Collector Groups page displayed the wrong help topic. (Jira ID: SLUI-20821)

  • Restored the Skylar AI icon for cleared anomaly and prediction events on the Events tab of the Device Investigator page. (Jira ID: SLUI-21725)

Events

  • Resolved an issue that prevented columns from being hidden when the table on the Events page was sorted or filtered by those columns. (Jira ID: SLUI-20413)

  • Addressed an issue that prevented the Enable Event Policy checkbox from being visible when the top navigation bar was set to a dark color while using a light theme. (Cases: 00321580, 00422365) (Jira ID: SLUI-21444)

  • Resolved an issue where the event policy's First Match String character limit was not enforced. (Case: 00395780) (Jira ID: SLUI-19762)

  • Addressed an issue that closed the browser window when the Create External Ticket button was clicked in the event table menu. (Case: 00469006) (Jira ID: SLUI-20898)

  • Resolved an issue where users with limited permissions could receive an error message when clicking the actions icon () on the Event Investigator, on the Events table, or on the Changes and Log Insights tables of the Service Investigator. (Case: 00498124) (Jira IDs: SLUI-21788, SLUI-21866)

  • Addressed an issue that prevented event notes from displaying in a CSV file exported from the Events page or the Event Dashboard widget. (Case: 00523119) (Jira ID: SLUI-22340)

  • Updated the "notifierLogs" GraphQL query so that running an event search returns only logs for events with event IDs included in the filter. (Case: 00524845) (Jira ID: SLUI-22340)

  • Resolved an issue where the Categorize events with an external system field on the Advanced tab of the Event Policy Editor page did not accept alphanumeric, punctuation, and special characters. (Case: 00553372) (Jira ID: SLUI-22657)

  • Resolved an issue where the Event Policy Editor page required Dynamic Application access that should not have been necessary for users with event policy permissions. (Case: 00534604) (Jira ID: SLUI-22583)

  • Resolved an issue where the Edit Note button on the Events page did not work when multiple events were selected on Global Manager systems. (Jira ID: SLUI-21131)

  • Improved the visibility of the Cancel button on the Event Policies page in Dark Mode. (Jira ID: SLUI-22338)

  • Resolved an issue where the device group list on the Event Policy Suppressions page displayed device groups that did not have event suppression visibility enabled. (Jira ID: SLUI-23615)

  • Restricted access to the Event Policy Suppression Editor to users with the required access hook aligned to their account. (Jira ID: SLUI-23616)

  • Resolved an issue that allowed users to delete event suppression records from outside their organization. (Jira ID: SLUI-22178)

Global Manager

  • Resolved an issue where SAML single sign-on for authentication in Global Manager provided users with incorrect permissions, resulting in increased or reduced access rights. (Case: 00492738) (Jira ID: SLUI-21564)

  • Resolved an issue where the graph in the Skylar Analytics Summary widget of the Event Investigator page did not load or display correctly when viewed through Global Manager. (Jira ID: SLUI-21073)

  • Resolved a caching issue in the Global Manager NextUI service that temporarily stored user information, allowing a different user to load the cached information. (Jira ID: SLUI-20931)

  • Resolved an issue where duplicated dashboards did not appear in the correct listing page on Global Manager systems. (Jira ID: SLUI-22784)

  • Resolved an issue where non-administrator users could not query all Global Manager stacks regardless of their organization alignment. (Case: 00588571) (Jira ID: SLUI-23168)

  • Resolved an issue that redirected users to child stacks by IP address instead of fully qualified domain name (FQDN) when clicking a managed device hyperlink on Global Manager systems. (Case: 00571716) (Jira ID: SLUI-23073)

  • Resolved an issue where the Version column on the Global Manager Stacks page was blank for stacks that used a virtual IP address in a high availability environment. (Case: 00622624) (Jira ID: SLUI-23532)

GraphQL

  • Resolved an issue where running the "GlobalManagerDeviceCategories" query with Global Manager enabled returned a null value for all queried fields except id. (Jira ID: SLUI-20601)

  • Resolved an issue that caused device GraphQL queries based on interfaces to fail. (Case: 00513430) (Jira IDs: SLUI-22069, SLUI-21560)

  • Resolved an issue where the "createDiscoverySession" GraphQL mutation produced an error when upgrading Skylar One (SL1) to version 11.3.1. (Case: 00360478) (Jira ID: SLUI-21434)

  • Resolved an issue that caused discovery sessions created using the "createDiscoverySession" GraphQL mutation to fail with an error. (Case: 00511630) (Jira ID: SLUI-22182)

  • Resolved an issue where GraphQL queries returned null results, causing an error, when searching for an organization with a null value. (Case: 00522745) (Jira ID: SLUI-22442)

  • Resolved an issue that prevented the "createGlobalManagerStack" mutation from working on systems running Skylar One (SL1) versions 12.3.6 through 12.3.9 with AP2 Nougat. (Jira ID: SLUI-23170)

  • Resolved an issue where the "createEventPolicy" mutation did not display clear error messages when the source field was missing or invalid. (Jira ID: SLUI-22550)

  • Resolved an issue where creating a universal credential using GraphQL could result in duplicate entries with the same type and subtype. (Jira ID: SLUI-22487)

  • Addressed an issue that caused GraphQL event policy update mutations to return outdated configuration values instead of the latest updates. (Case: 00574610) (Jira ID: SLUI-22996)

  • Resolved an issue where the "subscriptionLicenseUsageByDevice" query did not reliably return subscription license usage by device. (Case: 00583363) (Jira ID: SLUI-23178)

  • Resolved an issue where device path queries returned a fetch error when using certain process-based filter syntax. (Case: 00336564) (Jira ID: SLUI-23244)

  • Addressed an issue where queries for device assets returned a blank value for the Asset Tag field. (Case: 00484529) (Jira ID: SLUI-23199)

  • Resolved an issue where the GraphQL Browser page could not be hidden or restricted on a per-user basis using access hooks. (Case: 00589053) (Jira ID: SLUI-23154)

Installation and Configuration

  • Resolved an issue where the Add Bonding Interface modal did not display as intended when clicking the + Add Bonding Interface button in the Node Configuration Application. (Jira ID: SLUI-22285)

Maps

  • Resolved an issue where the Classic Maps page failed to load properly when attempting to log in to the default user interface (AP2) without accepting the End User License Agreement (EULA). (Jira ID: SLUI-20801)

  • Resolved an issue where the Organization field on the geographic map creation page displayed an error requiring an organization to be selected, even when one had already been chosen. (Jira ID: SLUI-22349)

  • Resolved an issue where devices or services could become aligned to multiple organizations if the organization assigned to a location changed, with only the most recent alignment shown on the Locations page. (Jira ID: SLUI-23254)

  • Resolved an issue where relationships visible on the Maps page in the classic user interface were not displayed for the same devices on the Maps page in the default user interface (AP2). Also resolved an issue where maps with large numbers of nodes and relationships could take up to five minutes to load. (Cases: 00619621, 00643369, 00624014) (Jira IDs: SLUI-23602, SLUI-23671)

  • Resolved an issue where Layer-2 topology maps did not display relationships for devices with dual-homed interfaces. (Jira ID: SLUI-23672)

Platform and Security

  • Resolved an issue that caused a "Receiving 504 Gateway Time-out" error when attempting to access the Audit Logs page. (Case: 00415120) (Jira ID: SLUI-21014)

  • Resolved an issue that caused password reset emails to direct users to the classic user interface, even when the password reset was requested from the default user interface (AP2). (Case: 00458525) (Jira ID: SLUI-20939)

  • Resolved an issue where Skylar One (SL1) version 12.2.1.2 showed the incorrect version number in the footer. (Jira ID: SLUI-20424)

Skylar AI

  • Resolved an issue where the Metric Type column on the Anomaly Detection page displayed the presentation ID for a metric instead of the presentation name. (Jira ID: SLUI-21510)

  • Resolved an issue where Skylar AI service connections created from the Service Connections page did not appear in the left sidebar of the Skylar AI page. (Jira ID: SLUI-22176)

  • Addressed an issue where the Skylar Analytics Summary panel on the Events page did not display timeline charts showing predictive alert data. (Jira ID: SLUI-22761)

System Administration

  • Corrected an issue where the Admin Notifier system warning banner could continue to display after the underlying events were cleared, even when no active events appeared in the Event Console. (Case: 00426805) (Jira ID: SLUI-23393)

System Update

  • Addressed an issue where the system update process crashed with a database error if all pre-upgrade tests were disabled before deployment. (Jira ID: EM-76396)

  • Resolved an issue where a post-update script could report success even after failing to update certain database tables, which could leave some device and message definition data missing. (Jira ID: EM-78700)

  • Addressed an issue where the pre-upgrade status did not include already-deployed appliances when the check was re-run after deployment completed. (Jira ID: EM-80138)

  • Improved the performance of the Skylar One user interface when loading deployment logs for stacks with a large number of appliances. (Jira ID: EM-80210)

  • Resolved an issue where package conflicts during system update caused false-positive staging results. (Jira ID: EM-80237)

User Interface

  • Resolved an issue that caused longer login times in the default user interface (AP2) for non-administrator users or users with limited permissions when using LDAP for authentication. (Cases: 00477960, 00478182) (Jira ID: SLUI-21012)

Upgrading Skylar One

You can consume Skylar One 12.3.16 only if you are upgrading from an earlier Skylar One version that supports upgrades to this release. There is no ISO version for version 12.3.16.

For a detailed overview of Skylar One, see the Introduction to Skylar One manual.

For detailed instructions on upgrading Skylar One, see the section on Updating Skylar One in the System Administration manual and the upgrade notes that are included in this document.

ScienceLogic strongly recommends that you review the Known Issues for Skylar One at https://support.sciencelogic.com/s/known-issues#sort=relevancy before installing a new update.

For known issues specific to this release, see the Known Issues section of this document.

Skylar One Extended Architecture

For existing on-premises deployments of Skylar One Extended Architecture, see the section on Upgrading Skylar One Extended Architecture in the System Administration manual for upgrade instructions. For help with technical issues, contact ScienceLogic Customer Support.

 New installations of Skylar One Extended Architecture are available only on SaaS deployments.

Important Upgrade Notes for Skylar One 12.3.16

This section includes important notes for upgrading existing Skylar One systems to the 12.3.16 release.

Unless otherwise stated, the information in this section applies to all users who are upgrading from previous Skylar One versions.

ScienceLogic strongly recommends that you review these notes in their entirety before upgrading to version 12.3.16.

Supported Upgrade Paths

The validated upgrade paths to version 12.3.16 are outlined below. Be advised that you can perform upgrades from one minor version to any later minor version within the 12.3.x series. However, as with all updates, ScienceLogic strongly recommends that you perform such upgrades in a test environment before implementing the upgrades in production environments.

The following are the validated upgrade paths:

  • 12.3.15 > 12.3.16

  • 12.3.11 > 12.3.16

  • 12.3.7 > 12.3.16

  • 12.2.7 > 12.3.16 (be advised there is a known issue that affects this upgrade path)

For more information about supported upgrade paths for Skylar One releases, see the Skylar One Recommended Upgrade Paths section in the System Administration manual.

Pre-Import Script for Upgrade Efficiency

Beginning with 12.3.10, the system update import experience was improved to make it faster and more efficient by allowing you to run concurrent imports. This feature is not enabled by default. To enable it, download the patch bundle you want to import, then run the following script:

silo_mysql -e "INSERT INTO master.system_settings_patcher (param, value, description) VALUES ('use_concurrent_import', 1, 'Use concurrent patch import');"

After running the script, you can start the import process.

Pre-Upgrade Script to Avoid Database Synchronization Failures

There is a known issue that might cause the upgrade to 12.3.16 to fail during post-update with a "Database Synchronization failed after 3 attempts" error in both the UI logs and the /var/log/em7/patch_manager.log file. For more information about this issue, including a pre-upgrade script you can run to avoid it, see https://support.sciencelogic.com/s/article/21802.

STIG Support

12.2.x and 12.3.x STIG-compliant users can upgrade to this release via one of the support upgrade paths so long as you have not consumed or upgraded to the 12.3.0 STIG release. If you previously deployed or upgraded to 12.3.0 STIG, you cannot upgrade to 12.3.16 STIG due to a known technical issue. If this scenario impacts you, contact your ScienceLogic account manager for more details.

Users who are currently on an 11.x MUD system cannot upgrade directly to this release. 11.x MUD customers should follow the 11.3 MUD conversion to 12.2.1.1 STIG re-ISO migration path; this process is documented in the ScienceLogic OL8 MUD Conversion Guide. (Ask your ScienceLogic contact for this manual.) After you are on 12.2.1.1 STIG, you can upgrade to later STIG releases, including this release.

When deploying a STIG-compliant configuration, port 7700, the Web Configuration Utility, and the Database Tool page are all disabled. In addition, concurrent PowerShell, concurrent SNMP, and concurrent network interface collection are not supported for these deployments.

Aurora 3 Support

AWS deployments that are using Aurora 3 can upgrade to Skylar One (SL1) 12.3.16. If you are currently deployed using Aurora 2, you can upgrade to Skylar One (SL1) 12.3.16 but must perform a post-upgrade Aurora 2 to 3 conversion. If you are on a SaaS-hosted AWS deployment, the ScienceLogic SRE team will complete this conversion. If you are on a customer-hosted AWS deployment, you must complete this conversion, with additional steps in the section on Updating Skylar One in the System Administration manual. Contact ScienceLogic Professional Services if you need assistance.

Upgrading MariaDB and Rebooting Skylar One

All Skylar One versions include important package security updates. To apply these updates, you must upgrade MariaDB and then reboot all Skylar One appliances. The following table specifies the required MariaDB version for each Skylar One version:

Skylar One Release Release Type Required MariaDB Version

12.3.16

Upgrade only

10.6.28

12.3.15

Upgrade only

10.6.18

12.3.14

Upgrade only

10.6.18

12.3.13

Upgrade only

10.6.18

12.3.12

Upgrade only

10.6.18

12.3.11

ISO and upgrade

10.6.18

12.3.10

Upgrade only

10.6.18

12.3.9

Upgrade only

10.6.18

12.3.8

Upgrade only

10.6.18

12.3.7

ISO and upgrade

10.6.18

12.3.6

Upgrade only

10.6.18

12.3.5

Upgrade only

10.6.18

12.3.4

Upgrade only

10.6.18

12.3.3

Upgrade only

10.6.18

12.3.2

Upgrade only

10.6.18

12.3.1

ISO and upgrade

10.6.18

12.3.0

ISO and upgrade

10.6.18

For instructions on updating MariaDB or rebooting the Skylar One system, see the section on Updating Skylar One in the System Administration manual.

If you would like assistance in planning an upgrade path that meets your security needs while minimizing downtime, contact your Customer Success Manager.

Clearing Skylar One Cache Post-Upgrade

After upgrading to version 12.3.16, you should clear your system cache to remove cached items from Skylar One (SL1) and prevent several potential issues that can occur post-upgrade due to caching. To do so, go to Misc > Clear SL1 Cache.

Required Ports

Beginning with SL1 12.2.0, if you have a firewall between your Database Server, data engine, and Administration Portal appliances, you should open TCP port 8200 to facilitate communication between those appliances.

For a full list of ports that must be open on each Skylar One (SL1) appliance, see the section on Required Ports for Skylar One in the Installation and Initial Configuration manual.

Python 2 Support Deprecation

Prior to SL1 11.3.0 , all Dynamic Application snippets, Execution Environments, Run Book Actions, and ScienceLogic Libraries utilized Python 2. With the introduction of Python 3 support in 11.3.0, ScienceLogic announced its intent to deprecate support for Python 2 in a future release.

The core SL1 platform switched to Python 3 with the 12.3.0 release. However, ScienceLogic will still include Python 2 in parallel with Python 3 on the 12.3.x line.

The Skylar One 12.5.1 release does not include Python 2 support. Any Python 2 content will stop working when an instance is updated to version 12.5.1 and later.

ScienceLogic has proactively migrated the product and the PowerPacks it supports to Python 3. However, any custom content in customer-created PowerPacks must be recreated utilizing ScienceLogic-provided enablement tools or migrated to Python 3 before consuming the 12.5.1 release.

For more information, see the Python 3 Resource Center on the ScienceLogic Support site.

Python 3.9 Execution Environment Support Deprecation

Users who currently use Python 3.9 execution environments for Dynamic Applications and Run Book Automations are advised that the Skylar One 12.3.0 release removed support for Python 3.9 and added support for Python 3.11. For more information, see the section Important Notes on Creating ScienceLogic Libraries in the ScienceLogic Libraries and Execution Environments manual.

Use of tmux When Using SSH

In Skylar One (SL1) versions 12.3.4 and later, the tmux utility is disabled by default if you are on a non-STIG deployment and access a Skylar One system using SSH. ScienceLogic strongly encourages non-STIG users on these versions to enable the tmux utility prior to using SSH sessions, such as for upgrading MariaDB, to avoid SSH sessions timing out after 15 minutes.

If you are on a STIG-compliant Skylar One deployment, or if you are on a non-STIG deployment between versions 12.2.1.1 and 12.3.3, the tmux utility is enabled by default.

The tmux utility, which is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen, strengthens session-control mechanisms and aligns with industry-wide security practices.

If tmux is enabled, sessions are automatically locked after 15 minutes of idleness or if an unclean SSH disconnect or dropped SSH connection occurs. Upon login, Skylar One checks for and attaches any detached tmux session if it finds one; otherwise, it starts a new session.

The utility also facilitates advanced features like scroll-back buffering with search, built-in clipboarding, multiple sessions and panes, detaching or attaching sessions, and session supervision or sharing.

To enable the tmux utility in non-STIG deployments: 

  1. Either go to the console of the Skylar One appliance or use SSH to access the appliance.

  2. Open a shell session on the server.

  3. Type the following at the command line to edit the silo.conf file:

    sudo visilo

  4. Change the following line in the [OS_HARDENING] section of the file to enable tmux:

    TMUX = true

    If the [OS_HARDENING] heading does not already exist in the silo.conf file, you must add that immediately above the TMUX = true setting.

  5. Save and quit the file. (:wq).

  6. Log out of Skylar One and then log back in. The tmux utility is now enabled.

For more information about tmux shortcuts and usage, see https://tmuxcheatsheet.com/.

System Update Notes

  • Skylar One updates overwrite changes to the configuration file /opt/em7/nextui/nextui.env. (For more details, see https://support.sciencelogic.com/s/article/1423.) ScienceLogic recommends that you back up this file before applying an update and then reapply your changes to this file.
  • ScienceLogic recommends that you run backups of your Skylar One system before performing a system update.
  • The Skylar One user interface will be unavailable intermittently during system update.
  • During the normal system update process, multiple processes are stopped and restarted. This might result in missed polls, gaps in data, and/or unexpected errors. ScienceLogic recommends that you always install Skylar One (SL1) releases during a maintenance window.
  • The Skylar One (SL1) system update process starts a background process that can perform any required post-upgrade tasks. The post-patch update process is automatically stopped after 24 hours. However, depending on the size of your database as well as the version from which you are upgrading, the post-upgrade tasks can take several days to perform. If the post-patch update process is stopped after 24 hours, the process will automatically re-start and continue processing from the point at which it was stopped. If you see an event that indicates the post-patch update process was stopped, you do not need to contact ScienceLogic support for assistance until you see the same event for three consecutive days.
  • When upgrading a large number of Skylar One appliances, you might encounter an issue where the deployment summary shows that deployment timed out for many of the appliances but, upon further inspection, you discover that the appliances actually deployed correctly. This is due to a lag in the deployment status reaching the Database Server after the default timeout value of 3600 seconds (1 hour). If you check back later, the issue should fix itself. If you would rather work around this issue, you can increase the timeout value. For instructions, see the section on Adjusting the Timeout for Slow Connections in the "Updating Skylar One" chapter of the System Administration manual.
  • When upgrading Skylar One on AWS stacks, you might receive an error message that the Data Engines failed to patch correctly. If this occurs, re-run the pre-upgrade tests and then run the patch again; this should result in the Data Engines updating correctly and the correct version then being reflected on the Appliance Manager page (System > Settings > Appliances).
  • After upgrading, to ensure proper data collection, you should go to the Appliance Manager page (System > Settings > Appliances), locate one of the Data Collector or Message Collector appliances, and click the lightning bolt icon to force configuration push for that appliance.

Known Issues for Skylar One 12.3.16

ScienceLogic strongly recommends that you review all Known Issues for Skylar One. For more information, see https://support.sciencelogic.com/s/known-issues#sort=relevancy.

The following known issues exist for Skylar One 12.3.16:

System Upgrade

  • 12.2.x and 12.3.x STIG-compliant users can upgrade to this release via one of the supported upgrade paths so long as you have not consumed or upgraded to the 12.3.0 STIG release. If you previously deployed or upgraded to 12.3.0 STIG, you cannot upgrade to 12.3.16 STIG due to a known technical issue. If this scenario impacts you, contact your ScienceLogic account manager for more details. (Jira ID: EM-74235)
  • In systems that have consumed a large number of Skylar One patch imports, the master_filestore.storage_system_patch database table might grow too large. If this occurs, then when you attempt to log in to Skylar One, you will be unable to do so and will instead receive an error message stating "The table 'organizations_log' is full" if logging in via the default user interface (AP2), or without an error message if logging in via the classic user interface. To address this issue, you should clean up any previous patch import files after deploying a new version on your Skylar One stack. (Jira ID: EM-75727)
  • During deployment, the siloupdate-deploy-local service might display the following log messages, although in both cases, the deployment task still ultimately completes:
    • On primary databases, it displays "Failed to enqueue storage object. Error: 'charmap' codec can't encode…" in journalctl. (Jira ID: EM-78481)
    • On secondary databases, it displays "ERROR 2002 (HY000): Can't connect to MySQL server on '127.0.0.1' (115)" in journalctl from the sl-otelcol post-install scriptlet. (Jira ID: EM-78479)
  • If MariaDB has an interruption during the postupdate process, the deployment is initially marked as failed. After MariaDB becomes available again, the Version Update will re-run and the appliance deployment will be marked as complete. (Jira ID: EM-78499)
  • Upgrades to 12.3.15 or later might fail during postupdate with a "Database Synchronization failed after 3 attempts" error in both the UI logs and the /var/log/em7/patch_manager.log file. This issue occurs when there is a conflict with the database schema update that must be applied. For more information about this issue, including a pre-upgrade script you can run to avoid it, see https://support.sciencelogic.com/s/article/21802. (Case: 00692025) (Jira ID: EM-80664)
  • When upgrading from 12.2.x to 12.3.16, the patch hook task might repeatedly fail on Administration Portals, Data Collectors, and Message Collectors during staging. This occurs because the initial patch hook attempt does not fully complete the postscript action for the siloupdate package, which leaves the /opt/em7/backend/system_patcher_status.py file out of date on the appliance. To work around this issue, contact ScienceLogic Support for a script that you can run from your Database Server that updates this file on the affected appliances, and then run staging again. (Jira ID: EM-81231)

Authentication

  • A known issue might prevent the system from automatically logging out inactive users after the defined login expiry period. (Jira ID: SLS-1933)
  • A known issue with session cache management might cause Skylar One to log you out unexpectedly, or prevent you from logging in again after a recent session. If you experience either issue, you can work around it by clearing the cache of your web browser before you log into the Skylar One user interface. For more information, see https://support.sciencelogic.com/s/article/13701. (Jira ID: SLUI-21011)
  • The Single Instance Login setting, which can be set on the Behavior Settings page (System > Settings > Behavior), is not working as designed for user accounts that use ASCII ADFS authentication. (Jira IDs: SLS-1559)

Business Services

  • The Anomalies tab on the Service Investigator page for device services might incorrectly display devices that have anomaly detection disabled, rather than showing only those devices with anomaly detection enabled. (Jira ID: EM-62884)

Credential Management and Discovery

  • The Search box that displays when creating a new credential during unguided discovery does not work. (Jira ID: SLUI-20777)
  • When using the SNMP Public V2 credential to discover devices, you might see an unhandled exception in the system log near the end of the discovery session, despite the devices being discovered successfully. (Jira ID: EM-59380)
  • When selecting two or more SNMP credentials to discover a device, if the first credential with the lower ID number contains incorrect information and the second credential with a higher ID number contains the correct information, the discovery logs will not be able to get an SNMP response. (Cases: 00289639, 00292649, 00422558) (Jira ID: EM-39681)

Dashboards

  • Classic dashboard reports cannot be scheduled. Attempting to do so results in a "report is blank" error appearing in the system log. (Jira ID: EM-61778)
  • On the Dashboards page in the classic user interface, a chart that is destroyed and rebuilt when the dashboard loads might not grow its y-axis to fit the data, or clamp a negative minimum value to 0, after a redraw. As a result, data above the chart’s axis maximum might be cut off at the top of the chart. (Jira ID: EM-81559)

Device Management

  • You cannot assign an icon to a device from the Devices page by clicking the Actions button (ellipsis menu) for that device and selecting Assign Icon. (Jira ID: SLUI-19763)

Discovery

  • When discovering an Skylar One appliance using SNMP v2 or v3 credentials, you might see one or both of the following unhandled exceptions in the system log: "UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)" and "TypeError: Incorrect padding". (Jira ID: EM-74484)

Enterprise Key Management Service (EKMS)

  • The sl-vaultmngt service might start before EKMS has been initialized. (Jira ID: SLS-1944)
  • Configuration backups do not include the master.vault_token table, so restoring from a config backup will not restore EKMS token data. Users who depend on full database restores for recovery should ensure this information is backed up by other means. (Jira ID: SLS-1948)

Events and Alerts

  • Skylar One might not generate a "Healthy" event for events that are remediated during a maintenance window. If this occurs, you can clear the event manually. (Jira ID: EM-74713)
  • You might experience an issue where device log maintenance mode alerts do not have the correct Event ID or might be missing the Event ID entirely. (Jira ID: EM-74052)

High Availability and Disaster Recovery

  • In disaster recovery configurations, virtual IPs might not transition when promoting a secondary node to a primary node. (Jira ID: EM-76091)

Licensing

  • You might encounter a "License record not found" critical event after an appliance's IP address changes, due to the Event Engine using the former IP address to verify the appliance's license information. If this occurs, log in to the appliance using SSH and restart the "EM7 Core: Event Processing Engine" process by running the following command:

    sudo systemctl restart em7_event

    (Jira ID: EM-74134)

Logging

  • A known issue might cause several log configuration files to conflict. Depending on the order in which the files are executed, this might cause errors for the sl_vault and slsctl logs, or it might block log rotation. To work around this issue, delete the config files ~sl_vault and ~slsctl. (Jira IDs: SLS-1105, EM-62134)

PowerPacks

  • When installing or importing a PowerPack, you might not be able to adjust the PowerPack's embedded license or license key type. (Jira IDs: EM-71507, EM-72515, EM-72716)

Skylar AI

  • The sl-otelcol-mgmt.py script shows blank values for the sl-otelcol, em7-platform-core, and nextui versions when connecting to Skylar AI, making it unclear which versions are actually installed, even though the status output reports the versions correctly. (Jira ID: EM-78655)
  • Supplying an open telemetry collector endpoint URL with a trailing slash can cause the endpoint to be rejected or fail validation. As a workaround, remove any trailing slash from the URL before saving. (Jira ID: EM-77859)

System Tools

  • On the OID Browser page (System > Tools > OID Browser), the Where Symbolic is like option for the Search where drop-down field might not work as intended. (Jira ID: EM-74326)

User Interface

  • In the default Skylar One user interface (AP2), the End User License Agreement (EULA) page might not display as intended for new user accounts. Conversely, it might display on pages that were iframed from the classic user interface, even after the user agrees to the EULA. This issue is occurring for ADFS, CAC, and AD authentication methods. (Jira IDs: EM-67851, SLS-1932)
  • In the default user interface (AP2), when opening the Account Permissions page (Registry > Accounts > User Accounts > wrench icon) for an existing user account, the Theme/Brand drop-down field does not initially display on the page. To work around this issue, refresh the page. (Jira ID: EM-76478)
  • The Expand and Contract buttons are not working as intended on the Dynamic Application Collections page (Devices > Device Manager > wrench icon > Collections). You can still expand and contract individual items on the page. (Jira ID: EM-72370)
  • The Access Keys page (System > Manage > Access Keys) might not count administrator users in the value displayed in the # Aligned Users column. To work around this issue, go to the Account Permissions page (Registry > Accounts > User Accounts > wrench icon) for the administrator users and re-save their permissions. (Jira ID: EM-74241)
  • When you bulk-select multiple event policies to align with a run book automation policy, additional event policies that you did not select might become aligned with that automation policy as well. (Jira ID: EM-70690)
  • In the classic user interface, the filter for Edit Date is not working as intended on the Inbound Email page (Registry > Events > Inbound Email). (Jira ID: EM-75291)

 

Known Issues Resolved in Available Releases

Several known issues that are present in 12.3.16 are resolved in other releases that are currently available.

Issues Fixed in Skylar One 12.5.1

  • The following known issues impacting this release are fixed if you upgrade to Skylar One 12.5.1 or later:
  • The post_update script might show errors referencing scripts in incorrect directories. For more information, see https://support.sciencelogic.com/s/article/16189. (Case: 00481367) (Jira ID: EM-71361)
  • The use of a percentage character (%) in a password will prevent firstboot from completing. (Jira ID: EM-72924)
  • SNMP v3 default authentication sometimes fails on new Message Collectors. For more information, see https://support.sciencelogic.com/s/article/16042. (Case: 00482414) (Jira ID: EM-71374)
  • If you attempt to reset your Skylar One password from the default user interface (AP2), the email link that is provided will direct you to the incorrect page.(Jira IDs: SLS-1544)
  • A known issue is causing PDF and XSLX Ticketing report types to fail to generate properly due to an OL8 incompatibility issue. For more information, see: https://support.sciencelogic.com/s/article/11649. (Jira IDs: EM-51131)
  • The "Support: Configuration File Validation" and "Support: Appliance Validation" Dynamic Applications in the "ScienceLogic Support Pack" PowerPack contain SQL queries with the keyword "function", which is a reserved keyword in MySQL 8.0. Because of this, you might see unhandled exceptions relating to those Dynamic Applications. This issue is fixed in version 109 of the PowerPack, which is included in Skylar One 12.5.1. (Jira ID: EM-72266)
  • In the classic user interface, when a user is required to reset their password, the new password fields appear far above where they normally would appear. (Jira ID: EM-74342)
  • In STIG deployments, the DashSL1 column does not display on the PowerPack Manager page (System > Manage > PowerPacks). (Case: 00465085) (Jira ID: EM-66815)
  • On the Organizations page (Registry > Accounts > Organizations), the filter-while-you-type feature is not working as intended in the Skylar AI Status column. (Jira ID: EM-71414)

Issues Fixed in Skylar One 12.5.20

  • The following known issues impacting this release are fixed if you upgrade to Skylar One 12.5.20 or later:
  • After deploying or upgrading to Skylar One 12.3.16, you might not be able to log in to the Web Configuration Utility or port 7700. To resolve this issue, reboot the Data Engine or restart the em7_sladmin service. (Jira ID: EM-78175)
  • After updating, you might experience a large number of nameless component devices or a large number of logs indicating that component devices cannot be created or updated because no mapping types are defined. (Case: 00584214) (Jira ID: EM-77898)
  • On Skylar One systems with healthy EKMS installations enabled on a passive node, or in systems where EKMS is disabled altogether, the slsctl health_check might mistakenly return a failure value. (Jira IDs: SLS-1404)
  • The System Uptime object ID (OID) form can be saved even when required fields are missing (null), despite showing an error. This might result in incomplete or invalid OID entries. (Jira ID: EM-77844)
  • You might encounter an issue where the Device Investigator is missing the options to add device vitals panels for CPU, Memory, or Swap. (Jira ID: EM-76034)
  • Clicking the printer icon to print a report on either the Device Processes page (Devices > Processes) or Windows Services page (Devices > Services) results in a blank page appearing rather than a modal of report options. To work around this issue, go to the Classic Devices page (Devices > Classic Devices), click the bar graph icon for the device you want to print a processes or services report for, select either the Process tab or Services tab, and then click the printer icon. (Case: 00503774) (Jira ID: EM-73062)
  • On the Admin Processes page (System > Settings > Admin Processes), the Runtime Offset column does not display any values. You can view the runtime offset value by editing the process. (Case: 00506663) (Jira ID: EM-73218)
  • Any user with basic privileges who has the access hooks EVT_SUPPRESSION_ADDREM, EVT_SUPPRESSION_REG_PAGE, and EVT_MANAGER_REG_PAGE assigned to their user profile can delete event suppressions regardless of their organization membership. (Jira ID: EM-72912)
  • A new, non-administrator user that has all of the Reporting access keys aligned to their user account cannot create a new scheduler or see the archived reports. (Jira ID: EM-72259)
  • After upgrading to 12.3.2 or later, custom themes and logos might not display on classic user interface pages. To work around this issue, clear the cache of your web browser. (Case: 00503523) (Jira ID: EM-72921)
  • You cannot monitor Windows devices with IPv6 addresses using WMI. You can use PowerShell or SNMP to monitor Windows devices that work with IPv6. (Jira ID: EM-73384)