Skylar One 12.5.21 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.5.21.

The Skylar One 12.5.21 release includes updates to the Windows agent, changes to the ScienceLogic REST API, improved performance for deployment logs in large environments, a new ability to monitor non-Windows services, and package and security updates. It also addresses several issues from previous releases.

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

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

AP2 version 8.34.116 (Pancake)is installed by default in Skylar One 12.5.21.

Before You Proceed

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

  • The 12.5.21 release is available only as a patch; there is no ISO version.

  • All Python 2 functionality was removed from Skylar One with the 12.5.1 release. If you still use Python 2 for custom code, you cannot upgrade to this or any later releases until your custom code is Python 3-compatible.

  • You can perform upgrades from one minor version to any later minor version within the 12.5.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 ScienceLogic-validated upgrade paths to version 12.5.21 are outlined below.

    • 12.5.20 > 12.5.21

    • 12.5.8 > 12.5.21

    • 12.5.7 > 12.5.21

    • 12.5.1 > 12.5.21

    • 12.3.15 > 12.5.21

  • 12.5.21 supports STIG deployments. However, STIG-compliant users should contact their ScienceLogic account managers for important information about upgrading to this release.

  • AWS deployments that are using Aurora 3 can upgrade to this release.

  • The Enterprise Key Management Service (EKMS) is enabled by default in 12.5.21.

  • There is a known issue impacting upgrades to 12.5.4 and later from the 12.3.4 through 12.3.6 releases that could result in deployment failure due to patch hook task issues. For more information about this issue as well as a workaround, see https://support.sciencelogic.com/s/article/20990.

  • When upgrading Skylar One to version 12.5.21 from 12.3.x or earlier, PowerPacks that use legacy encryption will become read-only. This issue does not impact upgrades from previous 12.5.x releases. For more information about this issue, including resolution steps, see https://support.sciencelogic.com/s/article/20806.

  • If you are currently on a version of Skylar One prior to 12.5.20 and you use local authentication with an MD5-hashed password, you will be required to reset your password when upgrading to Skylar One 12.5.20 or later.

  • Skylar One 12.5.20 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.

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

New Features and Enhancements in Skylar One 12.5.21

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

Agent

  • Skylar One version 12.5.21 includes Linux Agent v198, which was previously pinned to version 12.5.20, and Windows Agent v160, which includes the following enhancements since v155 was pinned to Skylar One 12.5.20:

    • Windows Agent v158:

      • Resolved an issue where Windows Server CPU usage could spike to 100% when Dynamic Applications and the SiloAgent service ran simultaneously. (Cases: 00616696, 00617152)

        Windows Agent v158 resolves a defect that was found in versions 156 and 157 that could result in the agent being uninstalled. For this reason, you should not install those versions and instead upgrade to Windows Agent v158 or later.

    • Windows Agent v159:

      • Addressed an issue where the Windows Agent incorrectly reported 100% utilization on memory, file system, and other metrics after upgrading to a newer agent version. (Case: 00632042)

    • Windows Agent v160:

      • Resolved a memory leak in the Windows SiloAgent service where memory consumption increased over time until the agent was restarted. (Case: 00653462)

      • Improved Windows Agent log monitoring to better handle log rotation and file truncation.

      • Added support for sending notices from the Windows Agent to Skylar One in scenarios where the agent installation or upgrade fails.

API

  • Requests to the /api/credentials/ Rest API endpoint no longer return passwords by default, even for Admin accounts. Contact Support if you need the previous behavior restored.

  • Added the following events-related REST API endpoints to expose new external ticket fields: ext_ticket_ref_2, ext_ticket_ref_3, force_ticket_uri_2, and force_ticket_uri_3.

Monitoring Policies

  • You can now create service monitoring policies for device types other than Windows devices, either manually or using a device template. With this update, elements in the classic Skylar One user interface that were previously labeled "Windows Services", such as page names or field labels, are now simply labeled "Services".

Platform and Security

  • Skylar One version 12.5.21 includes package updates to improve security and system performance.

System Update

  • Improved the performance of the Skylar One user interface when loading deployment logs for large environments. The system now more efficiently handles the retrieval and display of extensive log data for stacks containing numerous appliances.

Issues Addressed in Skylar One 12.5.21

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

Agent

  • Addressed an issue that caused all agents to lose connectivity after upgrading. (Case: 00675187) (Jira ID: EM-80305)

API

  • Resolved performance issues in AWS environments caused by high RDS load from API requests to the network interfaces endpoint (/api/interface), dramatically reducing execution time. (Case: 00639899) (Jira ID: EM-79914)

Credential Management and Discovery

  • Ensured that Dynamic Application discovery works as intended even when debugging on processes is enabled. (Case: 00653864) (Jira ID: EM-79729)

  • Added support for IPv4z and IPv6z interface types during discovery to ensure these address types are interpreted and discovered correctly. (Case: 00634036) (Jira ID: EM-79512)

Dashboards

  • Addressed an issue that caused the "Forecast: Contextual Device" widget on classic dashboards to show a perpetual loading state instead of displaying data. (Jira ID: EM-80162)

Data Collection and Retention

  • Resolved an issue where the master_dev.device_interfaces database table was being updated during data collection even when the interface data had not changed, resulting in unnecessary database write load. (Case: 00624048) (Jira ID: EM-79461)

  • Reduced the load time for the Device Processes page (Registry > Devices > Processes) in the classic user interface in AWS environments. (Case: 00613590) (Jira ID: EM-78960)

  • Ensured the Hosts File Update data maintenance task is able to make updates to the /etc/hosts file on a Skylar One Data Collector and finish successfully when it encounters a non-unicode character in its existing file content. (Case: 00668444) (Jira ID: EM-80241)

  • Resolved multiple issues that caused daily maintenance to take significantly longer than expected when pruning interface extended hourly and daily rollup data. (Case: 00678047) (Jira IDs: EM-80265, EM-80474)

Deployment and Configuration

  • Ensured that all generated AWS resource names stay within the 32-character AWS limit when deploying Skylar One in AWS. (Jira ID: DO-6283)

Events

  • Resolved an issue that sometimes prevented you from taking certain actions on the Classic Events page, such as clearing or acknowledging events. (Jira ID: EM-79905)

Platform and Security

  • Updated the /etc/logrotate.d/em7mysql file to add more robust log rotation. The new configuration ensures logs are correctly flushed and compressed, preventing the /var/log partition from reaching capacity. (Case: OO474964) (Jira ID: EM-71034)

PowerPacks

  • Addressed an issue that sometimes prevented users in STIG deployments from adding AP2 content objects to PowerPacks. (Jira ID: EM-78797)

Installing and Upgrading Skylar One

You can consume Skylar One 12.5.21 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.5.21.

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

For detailed instructions on performing a new installation of Skylar One, see the Installation and Initial Configuration 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.5.21

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

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

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

Supported Upgrade Paths

The ScienceLogic-validated upgrade paths to version 12.5.21 are outlined below.

  • 12.5.20 > 12.5.21

  • 12.5.8 > 12.5.21

  • 12.5.7 > 12.5.21

  • 12.5.1 > 12.5.21

  • 12.3.15 > 12.5.21

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.5.1, 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.

STIG Support

12.2.x and 12.3.x STIG-compliant users should contact their ScienceLogic account managers for information about upgrading to 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 network interface collection is not supported for these deployments.

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

Upgrade only

10.11.16

12.5.20

ISO and upgrade

10.11.16

12.5.8

Upgrade only

10.6.21

12.5.7

Upgrade only

10.6.21

12.5.6

Upgrade only

10.6.21

12.5.5

Upgrade only

10.6.21

12.5.4

ISO and upgrade

10.6.21

12.5.3

Upgrade only

10.6.21

12.5.2

Upgrade only

10.6.21

12.5.1

ISO and upgrade

10.6.21

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, please contact your Customer Success Manager.

Clearing Cache Post-Upgrade

After upgrading to version 12.5.21, 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 3.9 Execution Environment Support Deprecation

Users who are currently on 12.2.x releases and use Python 3.9 execution environments for Dynamic Applications and run book automations are advised that the 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

Starting with Skylar One (SL1) version 12.3.4, the tmux utility is disabled by default if you are on a non-STIG deployment and access a Skylar One (SL1) system using SSH. This is a change in behavior from versions 12.2.1.1 through 12.3.3, where the tmux utility was enabled by default.

If you are on a STIG-compliant Skylar One (SL1) deployment, the tmux utility is enabled by default. ScienceLogic encourages non-STIG users to enable the tmux utility as well.

The 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 (SL1) checks for and attaches any detached tmux session if it finds them; 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 (SL1) 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 (SL1) and then log back in. The tmux utility is now enabled.

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

Changes to High Availability and Disaster Recovery Configurations

In Skylar One (SL1) 12.3.2, the web server configuration for the vault service was updated to improve behavior between multiple database and data engine appliances. This was done to prevent false system events indicating that passive databases could not connect to Skylar One Collectors in high-availability (HA), disaster recovery (DR), or HA+DR configurations. With this update: 

  • On new installations, you must run the following command after all database and data engine appliances are licensed, to populate the list of allowed locations where vault could be running: sudo /opt/em7/share/scripts/vault_add_servers.sh. If the list is populated successfully, the output will tell you to restart nginx for it to take effect. Upon updating, this is generated automatically.

  • If you are upgrading and you have not modified the default configuration file, then it will be updated to this new configuration automatically.

  • If you are upgrading and you have modified the default configuration file, the updated web server configuration will be installed as /etc/nginx/conf.d/vault.conf.rpmnew, and you will need to merge your modifications into the new configuration and then remove the .rpmnew extension.

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 releases during a maintenance window.
  • The Skylar One 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.5.21

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.5.21:

Deployment and Configuration

  • Deployment might fail on remote appliances with a "Vault configuration error: decrypt" message. This typically occurs during the payload upload phase. To work around this issue, rerun the deployment task. (Jira ID: EM-79783)

System Upgrade

  • 12.2.x and 12.3.x STIG-compliant users should contact their ScienceLogic account managers for information about upgrading to this release.
  • The Patch hook task might fail on secondary Database Server and Administration Portal appliances when concurrent import is enabled during an upgrade. To work around this issue, manually upgrade the siloupdate RPM on the affected appliances. (Jira ID: EM-79882)
  • When upgrading Skylar One to version 12.5.21 from 12.3.x or earlier, PowerPacks that use legacy encryption will become read-only. This issue does not impact upgrades from previous 12.5.x releases. For more information about this issue, including resolution steps, see https://support.sciencelogic.com/s/article/20806.(Jira ID: EM-73018)
  • In systems that have consumed a large number of Skylar One (SL1) patch imports, the master_filestore.storage_system_patch database table might grow too large. When this occurs, login attempts to Skylar One fail and you will receive an error stating "The table 'organizations_log' is full" in the default Skylar One user interface (AP2), or it will fail silently in 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. For more information about this issue, see https://support.sciencelogic.com/s/article/18285. (Jira ID: EM-76040)
  • System updates sometimes fail on Data Collectors due to siloupdate not updating on them. For more information about this issue, including workaround procedures, see https://support.sciencelogic.com/s/article/18508. (Case: 00543539) (Jira ID: EM-76307)
  • After updating your system, you might experience an issue where the user interface is not displaying or working as intended. If this occurs, clear your browser cache. (Jira ID: EM-73859)
  • 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)
  • An intermittent issue sometimes causes the database connection to Amazon RDS instances to become unavailable for a brief amount of time during the upgrade process, which causes deployment to be marked as failed in the user interface. If this occurs, re-run the upgrade; doing so should update all backend metadata to register as successfully completed and update the latest version in the user interface. (Jira ID: EM-66627)
  • 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)
  • The MariaDB upgrade process might fail with an error stating that /opt/em7/services/config.env does not exist. This prevents the siloupdate utility from stopping ScienceLogic services before proceeding with the database upgrade. (Jira ID: EM-75840)
  • During a patch staging retry, an appliance that completes staging successfully might still be incorrectly reported as "Failed" in the staging summary. This is a reporting error and does not necessarily mean the files were not staged. (Jira ID: EM-79600)

Access Control

  • You might be able to delete an account policy even if it is currently assigned to active accounts or authentication resources, which can cause you to experience orphaned configurations and authentication issues. (Jira ID: EM-79801)
  • The system erroneously enables you to create an empty access key if you click Save without filling in any fields, which can lead to invalid or non-functional permission configurations. (Jira ID: EM-76409)

Agent

  • Clicking the Upgrade button on the Agents page results in a message indicating that the upgrade was successful immediately appearing at the bottom of the page, though the upgrade was merely initiated. The actual upgrade process can take several minutes to complete. (Jira ID: EM-74365)
  • When attempting to install a Gen 1 agent on an AWS stack, the installation user interface will display an incorrect IP for download, which will result in the download attempt failing. (Jira ID: EM-74307)
  • You might experience a scenario where an agent's polled data configuration is cleared unintentionally. (Jira ID: EM-74364)
  • Discovery via Streamer Prime fails for Gen 1 Agent devices if the existing device record has a class_type of 0. This typically occurs when a device aligns before its backing PowerPack is fully installed or populated. (Jira ID: EM-79395)
  • The Dead Letter Queue (DLQ) for streamer_push might erroneously indicate that it has exceeded its threshold. (Jira ID: EM-77934)

API

  • Deleting a user account via the REST API (DELETE /api/account/<uid>) does not archive the account in the master_access.accounts_deleted database table, thus allowing the next account created to reuse the deleted account’s user ID (uid). (Jira ID: SLS-2044)
  • The account API prevents the Aligned_organizations field from being set to null. As a result, users cannot disable additional organizations for a user via the API. (Jira ID: SLS-2081)
  • Attempts to update device filesystem or Dynamic Application thresholds using the API (POST/PUT) might result in a "System internal error". (Jira ID: EM-76562)

Asset Management

  • When creating or editing an asset, the values entered in the Administrator and Technician fields might not be saved. (Jira IDs: EM-74258, EM-76664)

Authentication

  • 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 ASCII ADFS user accounts. (Jira ID: SLS-1559)
  • If you create an empty authentication resource with no values filled in and assign it to an empty authentication profile, upon logging out of the system, the user interface becomes inaccessible. (Jira ID: EM-76608)
  • You might intermittently encounter an error message when attempting to change your password or submit preference changes on the Account Preferences page (Preferences > Account > Preferences). (Jira ID: SLS-1949)
  • If you attempt to save a single sign-on authentication resource without providing the required IdP Certificate, the form displays an error and resets all other fields, forcing you to re-enter all configuration data. (Jira ID: EM-79836)
  • Password policy fields (Password Expiration, Password Shadowing, Require Password Reset, Password Strength) may appear as null in user account policies and cannot be updated through the user interface. These fields can be set directly via the Skylar One REST API using the following fields: 
    • passwd_expiration. Valid values are 0 (never) or 30, 60, 90, 180, or 365 (days).
    • passwd_prev_count. Valid values are 0 (last year), 1–10 (cannot reuse last [#] passwords).
    • passwd_reset_required. Valid values are 0 (no) or 1 (yes).
    • passwd_strength. Valid values are 0 (good), 1 (strong), or 2 (very strong).

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)
  • For services that have their RCA Options field enabled and have had a child service removed, Skylar One 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 if the parent service has the RCA Options field Enabled, then set this field to Disabled if it is not already.

Credential Management and Discovery

  • For an unguided device discovery, the Search box that displays for creating a new credential 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)
  • The Credentials page in the default user interface (AP2) fails to display credentials that are not aligned with an organization, but displays these credentials correctly in the classic Skylar One user interface on the Credential Management page. (Jira ID: SLUI-20947)
  • On the Credentials page, if you have more than 50 credentials and at least one of the first 50 credentials is not aligned with an organization, the page will display duplicates of these credentials. (Jira ID: SLUI-20947)
  • You might get an error when trying to open SOAP/XML credentials that have been imported from a PowerPack. (Jira ID: EM-74291)

Dashboards

  • Creating an Interface widget with the Leaderboard visualization, applying an advanced filter, and adjusting the data time span using the Time span filter results in an error. (Jira ID: SLUI-22200)
  • When editing the scale prefix of a Device widget using the Leaderboard visualization, the Storage Used column does that update in that widget's table. (Jira ID: SLUI-22198)
  • When editing an Events widget and setting the Refresh Mode field to None, the widget's events table shows the refresh mode as automatic, despite the change. (Jira ID: SLUI-21947)
  • In classic dashboards, if you create a Traffic Light widget, the ability to control context in other subscribing widgets is not working as intended. (Jira ID: EM-76527)
  • You might encounter incorrect values in Business Service dashboards and device metric trend charts when viewing physical memory aggregations due to a mapping error in the normalized database views causing physical memory sum data to track CPU activity instead. (Jira ID: EM-79948)
  • The "Shared: Interface Billing" dashboard might generate a large number of console errors when loading, particularly on STIG systems. (Jira ID: EM-77611)
  • When imported via a PowerPack, the "Custom Table: Journal Apps" dashboard widget's settings might appear, but selections do not display correctly. (Jira ID: EM-76599)
  • The "Event Counts by Severity" widget fails to display any data when the event state is set to "Acknowledged," even if acknowledged events exist in the system. The widget correctly displays data only when set to "Unacknowledged." (Jira ID: EM-76286)

Data Collection and Retention

  • If you include an invalid or incorrectly typed value in silo.conf, such as a word or phrase where it should be an integer, the data pull process crashes and cannot start. (Jira ID: EM-74238)
  • When aligning a Dynamic Application that discovers a dynamic component map tree using Latin-1 and UTF-8 encoded device names and identifiers, you might receive "Illegal mix of collations" data storage errors in the system logs. (Jira ID: EM-74263)
  • Some performance metrics and alert formulas display values with excessive decimal places instead of rounding to two. (Jira ID: EM-79390)
  • Disabling interface collection can cause the "Interface Magic" service in the collector pipeline to crash with a ZeroDivisionError. (Jira ID: EM-72808)

Device Management

  • On the Devices page, when sorting your search by the Organization column, the inventory table will sort by Organization ID instead. (Jira ID: SLUI-21459)
  • The assigned organization for devices might not always update, even after performing a bulk alignment organization action on the Devices page. To work around this issue, refresh your browser immediately after completing the bulk alignment action. (Jira ID: SLUI-21483)
  • When sorting by columns on the Device Investigator page in Firefox, the table might continuously attempt to retrieve results unsuccessfully. (Jira ID: SLUI-21095)
  • The Device Categories page (Devices > Device Categories) fails to load properly whenever there is a category with a null ID. To work around this issue, go to the Device Categories page (System > Customize > Device Categories), locate the category with the null ID, and then remove that category by clicking the delete icon () next to the category.(Jira ID: SLUI-20731)
  • The number of unacknowledged events in the Device Overview panel of the Device Investigator page does not update despite acknowledging alerts on a device. To work around this issue, add a new "unackEvents" subquery to the "Device Insights" query, then use that subquery to collect and retrieve information on unacknowledged events. (Case: 00471966) (Jira ID: SLUI-20858)
  • When attempting to bulk delete devices or device components, a dialog message might indicate that some or all of the devices or components failed to delete, when in fact they were actually deleted. (Jira ID: EM-74351)
  • Device reports generated from the Classic Devices page (Devices > Classic Devices) might result in an "Uncaught TypeError" message appearing in the browser console, despite most reports generating correctly. (Jira ID: EM-74225)
  • HTML device journal reports might generate with no data. (Jira ID: EM-74286)
  • The checkbox to select all items on the Device Dashboards page (System > Customize > Device Dashboards) might select only the items that appear on your current page rather than all available device dashboards. (Jira ID: EM-74215)
  • Event messages in device logs for multi-match events might display with the incorrect event ID. (Jira ID: EM-74409)
  • After upgrading to 12.5.21, you might see multiple Attributes tabs on the Device Administration panel in the classic user interface. This issue does not affect ISO deployments. (Jira ID: EM-79933)
  • The trend checkboxes on the Performance tab of the Device Reports panel do not always accurately update the graph display. Additionally, unchecking a trend does not hide the area fill, and re-checking it causes the trend to disappear entirely. (Jira ID: EM-79776)
  • After successfully updating a device class on the Device Properties page, the system might erroneously display a "Device Class/Type Update Failed" error message. (Jira ID: EM-79472)
  • After un-aligning a custom attribute from a device, the Custom Attribute Subscriber modal might incorrectly display all devices in the system. This is a visual issue only; it does not impact the actual alignment status. (Jira ID: EM-76508)
  • Saving changes to a device's custom attributes might cause unset integer-based attributes to be automatically set to 0 rather than remaining null. (Jira ID: EM-76481)
  • Changes made to a device template during the "Modify By Template" process are not saved to the template itself, even when you select the Save When Applied & Confirmed checkbox, preventing you from updating persistent templates while applying them to devices. (Jira ID: EM-74696)
  • Nightly discovery might trigger a "TypeError" exception when updating interfaces for PowerShell-monitored devices. This issue appears in the storage process logs and affects the accuracy of interface IP updates. (Jira ID: EM-73781)
  • You cannot submit bulk administrative requests on the Device Components or Device Hardware pages in the classic user interface. A “Loading…“ message appears on the page and the submitted request fails. For more information, see https://support.sciencelogic.com/s/article/18343. (Jira ID: EM-73389)
  • The "System Vitals Performance" graph might display a blank screen if a device is missing a collection label. (Jira ID: EM-77642)

Enterprise Key Management Service (EKMS)

  • You might experience an issue where the EKMS state and vault contents disappear from your Data Collectors. If this occurs, you can work around the issue by going to the Appliance Manager page (System > Settings > Appliances) and manually running the Enterprise Database: Collector Config Push process to run on the impacted appliances. (Jira ID: EM-78522)
  • Configuration backups do not include the master.vault_token table, so restoring from a config backup will not restore Vault 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

  • Deviation alerting does not support the use of double quotes in indices. To work around this issue, use single quotes. (Jira ID: EM-72050)
  • The events on the Events page cannot be sorted by the Organization column. (Jira ID: SLUI-20903)
  • From the Event Policies page (Events > Event Policies), you can delete only a single event policy at a time, even if you select multiple event policies for bulk deletion. (Jira ID: SLUI-20853)
  • Event messages derived from incoming email substitute "\xc2" for the character Â. (Jira ID: EM-73551)
  • On the Event Statistics page, after changing the graph type (for example, from line to stepline), the checkboxes for showing or hiding trends and selections might stop functioning. The boxes remain unresponsive even if the graph type is changed back to the original setting. (Jira ID: EM-79888)

Global Manager

  • The devices on the Devices page in Global Manager systems cannot be sorted by the IP Address column. (Jira ID: SLUI-21108)
  • On Global Manager systems, the View Event Policy option in the Actions menu () on the Events page does not work as expected. (Jira ID: SLUI-21133)
  • On Global Manager systems, the Events page does not display events from child stacks. To work around this issue, clear all system caches on both the child stacks and the Global Manager parent stack, then restart the NextUI service. (Jira ID: SLUI-21134)

GraphQL

  • The "harProviderOnDemanProcessing" GQL query incorrectly creates a service table in the "data_har" database when executed with invalid or non-existent service IDs. (Jira ID: SLUI-21135)
  • Clicking the Run Now button for any Dynamic Application on the Collections tab of the Device Investigator will display the following GQL error message in the Skylar One server console: "Variable "$procId" of non-null type "ID!" must not be null." (Jira ID: SLUI-21070)

Logging

  • System logs related to backup start, stop, and failure events are not being generated as intended. While a backup might complete successfully, you cannot use the system logs to validate backup timelines or troubleshoot issues. (Jira ID: EM-79904)
  • A known issue might cause several log configuration files to conflict, which could cause you to see errors for the sl_vault and slsctl logs or potentially block log rotation in some cases, depending on the order in which the files are executed. To work around this issue, delete the config files ~sl_vault and ~slsctl. (Jira IDs: SLS-1105, EM-62134)
  • In debug mode, Config Push logs might show repeated "OperationalError: Partition management on a not partitioned table is not possible" messages. This log does not affect system functionality or appear in the user interface. (Jira ID: EM-79813)
  • The php-error.log does not track actions for non-administrator local users. (Jira ID: EM-77688)

Monitoring Policies

  • New Domain Name monitoring policies are successfully created only if you enter all required fields. If a required field is missed and you attempt to save, you must exit out of the modal and start again. (Jira ID: EM-80340)

Platform

  • You might receive an "Internal Server Error" when attempting to configure an IP address on a heartbeat interface using the Web Configuration Tool. To work around this issue, configure heartbeat IP addresses using the command line interface. (Jira ID: EM-79886)

PowerPacks

  • When upgrading Skylar One to version 12.5.21 from 12.3.x or earlier, PowerPacks that use legacy encryption will become read-only. This issue does not impact upgrades from previous 12.5.x releases. For more information about this issue, including resolution steps, see https://support.sciencelogic.com/s/article/20806.(Jira ID: EM-73018)
  • Due to a known issue, you might need to manually upgrade to the following PowerPack versions after installing or upgrading to Skylar One 12.5.1 or later:
    • "Net-SNMP Base Pack" v103 (Jira ID: EM-73518) 
    • "Microsoft Base Pack" v110 (Jira ID: EM-73516)
    • "Microsoft: Windows Server" v118 (Jira ID: EM-73516)
  • 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)
  • If a PowerPack installation fails, you are now prompted to contact ScienceLogic Support rather than being stuck on the installation page. (Jira ID: EM-77519)
  • You might encounter an issue that prevents you from deleting a PowerPack through the user interface. (Jira ID: 76085)
  • After updating the "ScienceLogic: Default Internal Events" PowerPack, the PowerPack Manager page might incorrectly display version 12.5.2 instead of version 100. (Jira ID: EM-79963)
  • If you use the "IBM: DB2" PowerPack, component information might not be available when the "IBM DB2: Dynamic Application Alignment" Run Book Policy and Action is run and the name of the parent component is unavailable to the Run Book Action. This will result in the additional Database-level Dynamic Applications being aligned with the Default SNMP credential. For more information, see https://support.sciencelogic.com/s/article/20838.
  • When creating a new PowerPack, attempting to save modifications without first refreshing the page might trigger an "Error: License key is not valid" message. To work around this issue, refresh the PowerPack Editor page. (Jira ID: EM-73201)

Reporting

  • If you create a PDF report about a single device from the Devices or Classic Devices pages (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface), some tables might not display as intended. (Jira ID: EM-79587)
  • The DEV_REPORT_CREATOR access hook currently only restricts the print icon on the classic Device Registry page. Users without this hook can still generate reports on the Device Properties page, on the Device Summary page, and in the default user interface (AP2). (Jira ID: EM-79956)
  • If you attempt to load a performance report with images, it will fail if the Percentile option is enabled on the graph. Reports without images are unaffected, but any report including visual graph data will fail to load in this state. (Jira ID: EM-79893)
  • The Notes section of generated User Report PDFs might display raw HTML tags instead of the intended rich text formatting. (Jira ID: EM-79867)
  • On the Report Output Styles page (Reports > Management > Report Output Styles), the Style Name column has values with non-breaking spaces that are displayed as HTML code. This issue does not prevent you from creating or running reports. (Jira ID: EM-80296)

Schedule Management

  • A large number of stored procedure calls over time can lead to memory growth in the scheduler process as well as delays in processing schedules. (Jira IDs: EM-76720, EM-75045)

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)
  • Anomaly Detection and Predictive Alerting are not created for Dynamic Applications that are not associated with a PowerPack. (Jira ID: EM-73074)
  • Skylar AI Connection debug always runs on the node the connection was initially configured with, even after a failover. When this occurs, it causes a false negative status. (Jira ID: EM-78209)
  • 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)
  • If the Skylar AI endpoint is unavailable, the Open Telemetry Collector might receive data from Skylar One but fail to send it to Skylar AI without notifying the sender. (Jira ID: EM-78343)

Subscription Billing

  • The Bandwidth Billing interface filter might become unusable after the initial search, even if the filter is cleared. To work around this issue, click Reset. (Jira ID: EM-76511)

System Administration

  • When editing a collector group from the Collector Groups page (Manage > Collector Groups) by clicking its Actions menu (ellipsis icon) and unchecking two or more organizations in the Limit access to specific organizations field of the Edit Collector Group modal, the Organizations column on the Collector Groups page will show that only one organization was deselected, even if multiple were. (Jira ID: SLUI-22167)
  • Message Collectors on the Collector Groups page (Manage > Collector Groups) cannot be sorted by the Message Collectors column. (Jira ID: SLUI-22099)
  • Default account policies might automatically align with the organization that is alphabetically ranked lowest, potentially causing unexpected policy assignments. (Jira ID: SLS-2084)

User Interface

  • In the Skylar One user interface, the End User License Agreement (EULA) page is displayed on all 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 ID: EM-67851)
  • 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. (Case: 00495396) (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)
  • Name changes to nodes on the Nodes page (Manage > Nodes) are not saved. (Jira ID: SLUI-22248)
  • 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)
  • On the OID Browser page (System > Tools > OID Browser), the Where Symbolic is like drop-down option for the Search where field might not work as intended. (Jira ID: EM-74326)
  • 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)
  • When using a dark mode theme, if you click on a calendar icon to select a date, some dates might not be visible on the calendar. (Jira ID: EM-76629)
  • The final row might not appear on the Select Objects page (System > Customize > Select Objects) when viewed in the default user interface (AP2) using a Firefox browser. (Jira ID: EM-74222)
  • When using Active Directory Federation Services (ADFS) to authenticate, the system opens to the default landing page rather than the last page the user visited. (Jira IDs: SLS-1764, SLS-1765)
  • If you create a new network on the IPv4 Networks page (Registry > Networks > IPv4 Networks), it might not appear on the page after you save it. However, the network should still be available for selection in other operations. (Jira ID: EM-76666)
  • In AWS deployments, the % Used column on the IPv4 Networks page (Registry > Networks > IPv4 Networks) might erroneously display values over 100%. (Jira ID: EM-76672)
  • When saving a change on the Quality of Service Threshold Defaults page (System > Settings > Thresholds > Quality of Service), the page might continuously state that it is saving until you refresh the page. Despite this messaging issue, the system should save the changes correctly. (Jira ID: EM-74336)
  • If you select a normalized option for a service usage graph, the Date Range Selection pane changes to the year 1970 and the graph will not be visible, even if you correct the start and end dates. (Jira ID: EM-74331)
  • When creating an uptime OID, the system might display an error alert if the OID is invalid but still save the OID anyway. (Jira ID: EM-74227)
  • On the Process Manager page (System > Settings > Admin Processes), if you deselect the appliance type(s) that a process should run on and then save that change, it will prevent that process from starting in the future. (Jira ID: EM-74236)
  • If you click the Save button on the User Policy Properties Editor page (Registry > Accounts > User Policies > create or edit) for an existing user policy, the system mistakenly saves the user policy again as a separate entry rather than overwriting the existing policy with the updated information. (Jira ID: SLS-1773)
  • The Sharing Permissions drop-down field on the Appliance Settings page incorrectly displays Private by default, even though the system treats the setting as Shared. (Jira ID: SLS-1870)
  • Going to some pages or performing certain actions in the classic user interface might trigger "PHP Deprecated" notices in the error logs. These notices do not impact page functionality and can be safely ignored. (Jira IDs: EM-79898, EM-75356, EM-75310)
  • The Save As button for Database type credentials might be invisible or partially obscured when using the Firefox browser. This issue specifically affects systems that have upgraded through multiple versions and is not present in other browsers. (Jira ID: EM-79885)
  • After performing an initial search in the Bandwidth Billing Policy Editor, the Filter button can become inactive, preventing users from changing the filter text. To work around this issue, click the Reset button. (Jira ID: EM-79847)
  • Sorting by the Organization column on the SSL Certificate Monitoring page might produce inaccurate results due to the system sorting by the organization ID rather than the organizations name. (Jira ID: EM-79843)
  • In classic Service Provider Utilities, Service Usage policies might fail to save selections if you choose more than one device. (Jira ID: EM-79809)
  • On the User Policy Membership page (Registry > Accounts > User Policies) in the classic user interface, sorting by the First Name, Phone, or Mobile columns might cause all rows to disappear, preventing administrators from managing policy members while the sort is active. (Jira ID: EM-74702)

Known Issues Resolved in Available Releases

  • The following known issue impacting this release is fixed if you upgrade to the AP2 version 9.13.1-14 (Quesito) release or later after upgrading to 12.5.21:

    • In systems with Skylar AI enabled, the sorting feature for columns on the Anomaly Detection page only sorts by the data currently displaying on the page, which might not include all anomaly detection data. (Jira ID: SLUI-22523)

    • Filtering the Collector Groups column on the Device Investigator page with multiple group names can cause the page to not load correctly. (Jira ID: SLUI-21035)

    • The column widths on the Device Investigator page do not adjust when resized. (Jira ID: SLUI-20081)