Skylar One AP2 Snickerdoodle version 9.53.0 Release Notes
The AP2 version 9.53.0 (Snickerdoodle) release improves Business Services scalability and management, redesigns the tab of the Device Investigator, and introduces a new Password Policy page. This release also includes package and security updates, and addresses several issues from previous releases.
AP2 releases are separate from Skylar One platform releases to provide updates and improvements more frequently.
These release notes provide a comprehensive list of the features, enhancements, and addressed issues that are included in this release.
Before You Install or Upgrade
Before you install or upgrade to AP2 Snickerdoodle 9.53.0, be advised of the following:
-
You must be running Skylar One version 12.5.8 or later to install this release. For details on upgrading Skylar One, see the appropriate Skylar One platform release notes.
-
AP2 Snickerdoodle 9.53.0 is not supported in 13.0.x versions of Skylar One.
-
This update is available for both on-premises and cloud-based (SaaS) Skylar One systems.
-
All Skylar One appliances in your stack must be on the same AP2 version.
-
The AP2 Snickerdoodle update must be administered to systems that host AP2.
Installing or Uninstalling AP2 Snickerdoodle
To install AP2 Snickerdoodle version 9.53.0 onto your system, you must download and install the AP2 Snickerdoodle TGZ bundle file from the ScienceLogic Support Center. This bundle contains three separate RPM files. You must install the AP2 RPM files on all appliances that host AP2, including Database Servers (All-In-One Appliances, central databases, disaster recovery database servers, and high availability database servers) and Administration Portals. For AWS systems, you must install the RPM files on all relevant data engines.
The following instructions provide an example for installing AP2 Snickerdoodle on a Database Server. These steps are also applicable to other AP2 hosting systems.
To install AP2 Snickerdoodle version 9.53.0:
-
If you have not already done so, install or upgrade your Skylar One system to version 12.5.8 or above. For more information about upgrading to those releases, see the appropriate Skylar One platform release notes.
-
Go to the ScienceLogic Support Center and download the Snickerdoodle TGZ file locally to your machine from the AP2 Release Versions page (Skylar One > Downloads > AP2 Releases). To do so, select "Snickerdoodle" from the Release Files table and then click the button located under the Release File Downloads section of the page.
Depending on your browser or operating system, the TGZ file might download as a TAR file.
-
Either go to the console of the Skylar One Database Server or use SSH to access the Database Server.
-
For AWS systems: At the shell prompt, copy the RPM file to your Skylar One system by running the following command:
- <aws-system-pem> is the PEM file for the AWS system.
- <Snickerdoodle-ap2-version> is the AP2 Snickerdoodle release version.
- <system-ip-address> is the IP address of your Skylar One system.
-
For on-premises systems: At the shell prompt, copy the RPM file to your Skylar One system by running the following command:
- <Snickerdoodle-ap2-version> is the AP2 Snickerdoodle release version.
- <system-ip-address> is the IP address of your Skylar One system.
scp -i <aws-system-pem>.pem -o StrictHostKeyChecking=no nextui-<Snickerdoodle-ap2-version>.release.tgz em7admin@<system-ip-address>:/home/em7admin/
where:
scp -o StrictHostKeyChecking=no nextui-<Snickerdoodle-ap2-version>.release.tgz em7admin@<system-ip-address>:/home/em7admin/
where:
-
-
Install the AP2 TGZ or TAR file on the Database Servers and the Administration Portal by running the following commands on those systems:
-
For TGZ files:
-
For TAR files:
tar -xzf nextui-<Snickerdoodle-ap2-version>.release.tgz
where <Snickerdoodle-release-ap2-version> is the AP2 Snickerdoodle release version.
tar -xf nextui-<Snickerdoodle-ap2-version>.release.tar
where <Snickerdoodle-release-ap2-version> is the AP2 Snickerdoodle release version.
-
-
Finish the installation by running the following commands:
cd nextui-<Snickerdoodle-ap2-version>.release
where <Snickerdoodle-ap2-version> is the AP2 Snickerdoodle release version.
sudo sh install-nextui-<Snickerdoodle-ap2-version>.release.sh
where <Snickerdoodle-ap2-version> is the AP2 Snickerdoodle release version.
-
Enter y to confirm the installation of the AP2 RPM file.
-
Reload the daemon service by running the following command:
sudo systemctl daemon-reload
-
Restart the NextUI service by running the following command:
sudo systemctl restart nextui.service
AP2 is inaccessible for a few minutes after restarting the NextUI service.
To uninstall the Snickerdoodle release features for AP2 version 9.53.0:
-
If you are currently on Skylar One version 12.5.8 or above and want to roll back to a previously installed AP2 release, download the RPM file for that earlier release from the AP2 Release Versions page (Skylar One > Downloads > AP2 Releases) on the ScienceLogic Support Center. To do so, select the name of the AP2 release you want to roll back to from the Release Files table and then click the button located under the Release File Downloads section of the page.
-
After you have the AP2 RPM files downloaded locally, either go to the console of the Skylar One Database Server or use SSH to access the Database Server.
-
For AWS systems: At the shell prompt, copy the RPM file to your Skylar One system by running the following command:
- <aws-system-pem> is the PEM file for the AWS system.
- <rollback-ap2-version> is the rollback AP2 version.
- <system-ip-address> is the IP address of your Skylar One system.
-
For on-premises systems: At the shell prompt, copy the RPM file to your Skylar One system by running the following command:
- <rollback-ap2-version> is the rollback AP2 version.
- <system-ip-address> is the IP address of your Skylar One system.
scp -i <aws-system-pem>.pem -o StrictHostKeyChecking=no nextui-<rollback-ap2-version>.rpm em7admin@<system-ip-address>:/home/em7admin/
where:
scp -o StrictHostKeyChecking=no nextui-<rollback-ap2-version>.rpm em7admin@<system-ip-address>:/home/em7admin
where:
-
-
Install the RPM file on your device by running the following command:
sudo rpm -U --force --replacefiles nextui-<rollback-ap2-version>.rpm
where <rollback-ap2-version> is the rollback AP2 version.
-
Reload the daemon service by running the following command:
sudo systemctl daemon-reload
-
Restart the NextUI service by running the following command:
sudo systemctl restart nextui.service
AP2 is inaccessible for a few minutes after restarting the NextUI service.
New Features and Enhancements in AP2 Snickerdoodle version 9.53.0
This section describes the features and enhancements that are included in Skylar One AP2 Snickerdoodle version 9.53.0.
Business Services
-
You can no longer delete a service policy that is aligned to an existing service.
-
Improved scalability: Services now support a maximum of 5,000 constituents per service. The default remains 100; contact ScienceLogic Support if you want to adjust the number of supported constituents in your system.
-
Improved the performance and reliability of retrieving service performance data for business services with a large number of constituents.
-
You can now realign multiple business services to a different service policy simultaneously from the Business Services page, so long as the selected services share a common type.
-
You can now set a custom default service policy for each service type (Device, IT, Business, and Aggregate). A new service inherits the default policy for its type.
-
Added an Advisories swimlane to the Service Investigator timeline for Skylar AI advisory events.
Device Management
-
Redesigned the tab of the Device Investigator.
-
Added Collector Name and Collector ID columns to the Devices page to identify the specific Data Collectors aligned to your devices.
-
Added a new Collector Group field on the Device Investigator's Info panel that lists the name and ID of the collector group aligned to the device. Additionally, updated the existing Collector field, which previously displayed the device's collector group, to instead identify the name and ID of the Data Collector aligned to the device.
-
Changed the "Windows Services" monitoring policy label to "Services" throughout the user interface.
Event Management
-
Added External Ticket 2 and External Ticket 3 as optional columns that can be included on tables that list cleared and masked events. Also, added the ability to use these columns to filter active and cleared events tables.
-
Added a banner with a link to Skylar Advisor at the top of the Event Investigator page for Skylar AI advisory events.
-
Added the ability to filter event tables by the Age column. You can filter by an absolute date range using the Between, Before, After, or At options, or by a relative age.
GraphQL (GQL)
-
Ensured that you cannot add a Global Manager system as a stack using the createStack mutation.
-
Added the cbqosObjectsByInterface query to support listing Class-Based Quality of Service (CBQoS) policies per interface in GQL.
-
Expanded interface queries and mutations in GQL to support all available interface properties.
-
Added a new updateDefaultHarPolicies mutation to manage default policies for each service type.
Platform and Security
-
AP2 version 9.53.0 (Snickerdoodle) includes package updates to improve security and system performance. These package updates include security updates that address the following known vulnerabilities: CVE-2026-19481, CVE-2026-19484, CVE-2026-74866, CVE-2026-87776.
-
Added a configurable list of trusted reverse proxies. Skylar One now accepts the X-Forwarded-For request header only from the proxies you list in /etc/nginx/conf.d/trusted-proxies. The shipped file trusts every address by default, so you must edit the list if you want to limit the proxies trusted. Any edits you make are retained when you upgrade.
System Administration
-
Added a new Password Policy page (System > Settings > Security > Password Policy), where you can configure password policy settings globally or for specific organizations, user policies, or user accounts. This page appears only in the default user interface (AP2); there is no classic user interface equivalent.
User Interface
-
Added an optional user preference page where you can set a timezone and a date and time display format for AP2 native pages. This page is disabled by default; an administrator can enable or disable it on a Skylar One stack using the settingsUseDateTimeUserPreferences GQL feature toggle.
-
Updated date and time selection throughout the user interface with a four-column picker (hours, minutes, seconds, AM/PM). This replaces the previous analog clock views.
Issues Addressed in Skylar One AP2 Snickerdoodle version 9.53.0
This section describes the issues that were addressed in Skylar One AP2 Snickerdoodle version 9.53.0.
AP2
-
Addressed an issue where custom Dynamic Applications displayed incorrect enumerated values in AP2 while displaying the correct values in the classic Skylar One user interface. (Case: 00706601) (Jira ID: SLUI-24204)
-
Resolved an issue where the subscription usage crunch process failed with a "TypeError: 'NoneType' object is not subscriptable" error. (Case: 00659300) (Jira ID: SLUI-24172)
Business Services
-
Addressed an issue where Business Service dashboard widgets could take eight to 18 seconds to load, or time out, in a Global Manager deployment with a large number of managed stacks. (Jira ID: SLUI-24232)
-
Addressed an issue where the Service Analysis tab on the Business Service Overview page displayed an empty table after you renamed the policy assigned to a device service. (Jira ID: SLUI-23880)
Credentials
-
Resolved an issue where the Credentials page in the default user interface (AP2) failed to display credentials that were not aligned with an organization, but displayed these credentials correctly in the classic user interface on the Credential Management page. (Jira ID: SLUI-20947)
-
Resolved an issue on the Credentials page, if you had more than 50 credentials and at least one of the first 50 credentials was not aligned with an organization, the page displayed duplicates of these credentials. (Jira ID: SLUI-20947)
Dashboards
-
Addressed an issue where an Interface widget on an AP2 dashboard could not link to the tab. (Case: 00691529) (Jira ID: SLUI-24087)
-
Resolved an issue where a dashboard containing a widget using the Number visualization could not be printed. (Jira ID: SLUI-23954)
Device Management
-
Removed the Insights section from the Device Overview widget in the Device Investigator. The section previously displayed inaccurate automation and unacknowledged-event counts. (Case: 00471966) (Jira IDs: SLUI-24100, SLUI-23565, SLUI-20858)
-
Addressed an issue where the Agents page displayed an error message on systems with installed agents. (Jira ID: SLUI-23497)
-
Resolved an issue where the bottom of the Device Overview widget was cut off in the Device Investigator. (Jira ID: SLUI-22663)
Global Manager
-
Deprecated the authentication field in the Accounts GQL endpoint and replaced it with the authenticationMethod field. (Jira ID: SLUI-24321)
-
Addressed an issue where the GM_STACK_TIMEOUT_MS setting was not applied, causing Global Manager requests to managed stacks to time out at the default value instead of the configured value. (Case: 00709051) (Jira IDs: SLUI-24186, SLUI-24252)
GraphQL (GQL)
-
Addressed an issue where an existing GraphQL (GQL) script failed with an "Invalid cursor supplied" error. (Case: 00692508) (Jira ID: SLUI-24094)
System Administration
-
Resolved an issue where a user did not consistently receive a custom theme or other account policy settings after those settings changed following the user's initial alignment to the policy. (Case: 00682810) (Jira ID: SLUI-24171)
Known Issues
The following known issues affect version 9.53.0 of the Skylar One AP2 Snickerdoodle release:
Business Services
-
On the Business Services page and the Devices page, converting a basic filter to an advanced search filter and then clearing the advanced filter can cause the page to crash. To work around this issue, refresh the page. (Jira ID: SLUI-23674)
-
On the Business Services and Devices pages, searching by name, opening a record, and then returning to the list can cause the search field to stop working correctly. To work around this issue, click the gear icon next to the search field and click a second time. (Jira ID: SLUI-24160)
-
The Time Taken to Complete HAR Refresh and Time Taken to Complete Hierarchy Calculation line chart widgets on the Service Insights page (Business Services > Service Insights) might display data that goes back further than seven days, and might appear empty on systems that have not yet accumulated sufficient data. (Jira IDs: SLUI-23818, SLUI-23816)
-
When creating a service from a template, the resulting service might receive a copy of the policies, even if the Make copy of policies checkbox is not selected. (Jira ID: SLUI-23102)
-
The filter to select devices or services during service creation from templates is not editable. (Jira ID: SLUI-23247)
-
With DEBUG logging enabled, the Business Service Management export path can log an "OSError: Message too long" error when a log record exceeds the syslog datagram size. (Jira ID: SLUI-23972)
-
When Business Service Management metric export is enabled, the OpenTelemetry export can repeatedly log an "Invalid type NoneType" exception for ruleset-level records that have no rule ID. (Jira ID: SLUI-23970)
Dashboards
-
Editing the scale prefix of a Devices widget using the Leaderboard visualization does not update the Storage Used column in the widget's table. (Jira ID: SLUI-22198)
-
Creating a Devices widget using the Line Chart visualization, then toggling on Area Chart and then selecting either Percentage or Normal from the Stack Options field, can cause the line chart to not display. (Jira ID: SLUI-22592)
-
When editing a Devices widget that uses storage metrics, selecting a scale prefix and saving does not apply the change. The scale prefix selection is not retained after saving. (Jira ID: SLUI-23777)
-
In a Devices widget using the Table visualization, columns for configuration Dynamic Application objects cannot be resized; dragging the column boundary snaps back as soon as you release it. (Jira ID: SLUI-24322)
-
When creating or editing a Devices widget using the Table visualization with the checkbox selected and Dashboards selected from the Link type field, removing the selected dashboard causes the button to disable, preventing the widget from being saved. (Jira ID: SLUI-23172)
-
Editing an Events widget and setting the Refresh Mode field to None still displays the refresh mode as automatic in the widget's event table. (Jira ID: SLUI-21947)
-
When a File Systems widget using the Leaderboard Bar Chart visualization is driving a subscribed table and multiple selections are made in the bar chart, the "%" unit label appears in the Data Used column of the table instead of the correct kilobyte (kB) unit. (Jira ID: SLUI-10317)
-
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 a widget using the Line Chart visualization, deleting the default "0" in the Threshold Line field prevents the widget from being saved. (Jira ID: SLUI-22591)
-
In widgets using the Table visualization that have specific entity selections, deleted entities might still appear in the widget configuration after those entities are removed. (Jira ID: SLUI-23229)
-
Using the Comfortable density setting in widgets with the Table visualization might cause the "Find column" menu under Column Preferences to not display column options until the widget is resized. (Jira ID: SLUI-23171)
-
When editing a widget in the Edit Widget modal, if a dashboard has a driving and subscribing widget connected by a custom context, toggling on the and saving the widget causes the custom context to disappear from the context drop-down field when the toggle is re-enabled, even if the subscribing widget is still using that context. (Jira ID: SLUI-23151)
-
The Select All checkbox on the Dashboards page only applies to dashboards that are currently loaded and visible in the list, and does not include additional dashboards that load as you scroll down. (Jira ID: SLUI-23686)
-
A noticeable delay might occur when interacting with dashboard widgets, such as creating a widget, selecting metrics and properties, or editing a widget. (Jira ID: SLUI-23901)
-
Users without the TKT_ACCESS_EXTERNAL access hook can still add the External Ticket, External Ticket 2, or External Ticket 3 column to an Events dashboard widget and view its values. (Jira ID: SLUI-24076)
-
When you edit an existing Service widget that was configured with all available Service Type options, the widget might revert to the Business Service type after you save it, even if you do not change any field. (Jira ID: SLUI-24064)
Device Management
-
On a device's tab, aligning or unaligning an extended custom attribute and then clicking can display a false "An error occurred while saving" message, even though the change saves correctly. To work around this issue, refresh the page; the attributes grid then reflects the change correctly. (Jira ID: SLUI-24259)
-
On the tab of the Device Investigator, expanding threshold cards in Firefox can display a styling issue. (Jira ID: SLUI-24107)
-
On the tab of the Device Investigator, a threshold value and its unit might be truncated when both are long. For example, a value of "10000" with the unit "interfaces" might display as "10 interfaces". (Jira ID: SLUI-24340)
-
In the device Info box, editing and saving only one of the Organization, Device Class, or Device Name fields displays the original value again when you reopen the Info box within the same page session. To work around this issue, reload the page. (Jira ID: SLUI-24189)
-
On the Devices page, when sorting your search by the Organization column, the inventory table sorts 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)
-
You might experience an issue where the Devices page loads only the first 30 devices and otherwise continually indicates that the page is loading. (Jira ID: SLUI-23248)
-
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 delete that category by clicking the delete icon (
) next to the category. (Jira ID: SLUI-20731) -
If you edit a device's name from the blue menu bar at the top of the Device Investigator, the button might become disabled. If this occurs, refresh the page to re-enable the button. (Jira ID: SLUI-24418)
Discovery
-
In the guided and unguided discovery wizards, the Collector drop-down field does not visually reflect the selected value, instead displaying "[object Object]". The button is also not disabled when no collector is selected. To work around the display issue, click and then in the wizard (or cancel and reopen the wizard) to force the step to re-render with the correct collector name. (Jira ID: SLUI-24290)
Events
-
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)
-
The event age shown on the Events page might not match the age shown on the Classic Events page, which can cause a discrepancy between the events that display based on the Age column filter depending on which page you are viewing. (Jira ID: SLUI-24125)
-
The External Ticket, External Ticket 2, and External Ticket 3 values appear as clickable links on the Events page but as plain text on the event details page. (Jira ID: SLUI-24124)
-
Pasting text into the code view of the event policy Description field and saving immediately might not save the change; editing and saving the policy a second time saves it correctly. (Jira ID: SLUI-24103)
-
Some event policy descriptions might not render correctly on the Event Policy Editor page. (Jira ID: SLUI-24102)
-
Filtering the Last Edited column on the Event Policies page (Events > Event Policies) by a date or time range might return no results, even when matching event policies exist. (Jira ID: SLUI-21029)
Global Manager
-
On a Global Manager system, the stack cache does not refresh after a credential aligned to a child stack is updated, which can cause queries against that stack to use a stale credential. (Jira ID: SLUI-24288)
-
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)
-
On Global Manager systems, the ID column in organization widgets and device widgets now displays the organization's GUID rather than the intended stack ID and organization ID. (Jira ID: SLUI-22654)
GraphQL (GQL)
-
The monitorSslCertificates query can fail with a "Failed to fetch monitors data" error. There is no workaround for this query directly, but you can retrieve the same SSL certificate monitor data through the device query instead. (Case: 00715444) (Jira ID: SLUI-24235)
-
The harProviderOnDemandProcessing query incorrectly creates a service table in the data_har database when executed with invalid or non-existent service IDs. (Jira ID: SLUI-21135)
-
The monitorMetricDataSearch query for device monitor metrics returns an internal server error. (Jira ID: SLUI-23619)
-
Clicking the button for any Dynamic Application on the tab of the Device Investigator displays the following GQL error message: "Variable "$procId" of non-null type "ID!" must not be null." (Jira ID: SLUI-21070)
-
In the GQL browser, the auto‑complete suggestions for queries and mutations can fail to load and instead show an error in the user interface and browser console, preventing type‑ahead help while editing requests. (Jira ID: SLUI-23433)
-
The deviceTraceRoute mutation might return an error instead of running the traceroute. (Jira ID: SLUI-24157)
-
A query for Dynamic Application metric data on a device might return empty results when that device is retrieved as part of a multi-device search, even though the same query succeeds for a single device. (Case: 00699859) (Jira ID: SLUI-24126)
-
In Global Manager, the deviceThresholds query does not support the globalManagerStackSearch filter. To request thresholds for a device on a managed stack, use a stack-prefixed device ID. (Jira ID: SLUI-24038)
Maps
-
When creating or editing a geographic map, filters applied in one map might be hidden if the related column is hidden in another map. To work around this issue, click the gear icon (
), select Column Preferences, and then click Show All. Alternatively, you can click the gear icon (
) next to the filter field (used to search devices or services) and select Clear. This prevents columns from being hidden or shown while preserving your applied filters. (Jira ID: SLUI-22809)
Skylar AI
-
If you click on a device name link on the Anomaly Detection page, a different device record might open. (Jira ID: SLUI-24391)
System Administration
-
When editing a collector group from the Collector Groups page (Manage > Collector Groups) by clicking its Actions menu (ellipsis icon) and clearing 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 shows 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)
User Interface
-
Name changes to nodes are not saved on the Nodes page (Manage > Nodes). (Jira ID: SLUI-22248)
-
The filter for columns where you can select a date (such as on the Events or Event Policies pages) might show an error in the browser console when using the "Before," "After," or "At" options. (Jira ID: SLUI-23421)
-
The Skylar AI icon still appears in the basic menu even after the Skylar AI connection is disabled. (Jira ID: SLUI-23327)
-
Clicking once on a table-based list page (such as Devices, Business Services, Events, Maps, or Dashboards) might not clear the filter if clicked shortly after typing in a column filter; click a second time to clear it. (Jira ID: SLUI-24108)
-
After you upgrade to AP2 version 9.53.0 (Snickerdoodle), if your browser uses a non-U.S. locale, the dates and times that display in inventory tables throughout the user interface might conform to the format used by your browser's locale rather than the original U.S.-style format. (Jira ID: SLUI-24399)