Discussion Forums
A place for dialogue and discovery about our products and services
Resource Library
Access our collection of helpful videos, guides, templates, and more
User Groups
Connect with members that have common interests or goals
Node Navigation
Featured Content
Recent Content
Cisco: UCS Manager v106 PowerPack Release Notification
We are pleased to announce that the Cisco: UCS Manager v106 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZSmCAO/cisco-ucs Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Updated the PowerPack for Python 3.11 compatibility. Improved the security of the PowerPack by implementing secure XML parsing that disables external entity resolutions, thereby preventing XML External Entity (XXE) vulnerabilites. Addressed an issue that occurred when upgrading to version 105 of the "Cisco: UCS Manager" PowerPack which caused collection errors for multiple Dynamic Applications. The issues were resolved by replacing the libsxlt library with a lxml Python library for the "Cisco: UCS Service Profile Discovery" Dynamic Application and by implementing minor updates to syntax strings for the remaining affected Dynamic Applications. (Case: 00523074 Please refer to the Cisco: UCS Manager v106 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: UCS Manager v106 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: UCS Manager v106 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: UCS Manager v106 PowerPack Release can be found in the Release Notes.
Update Device State Signal 15
The process Process 'Update Device State' has a default frequency of 1 min, but we have a large number of device groups, over a thousand, i see this every minute 'already running, not starting, proc name Update Device State' And after a few minutes it then sends a signal 15, and terminals the process 'Process Update Device State has caught signal 15 and is exiting.' I'm wondering whats the implications if i change the time factor to allow the process to run longer, or if there is an limitation to the number of device groups that should be allowed?Recent updates to docs.sciencelogic.com
12/5/25 Documentation updates to the main docs site at https://docs.sciencelogic.com/ Updated the Skylar Compliance SyncPack manual to reflect changes made for version 3.0.0 , including the rebrand of Restorepoint to Skylar Compliance. Updated the Skylar Compliance manual to reflect changes made for the 20251203 maintenance release. 12/5/25: Documentation updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Added release notes for the Net-SNMP Base Pack v104, which updates Dynamic Applications to ensure compatibility with PHP 8 standards. Added release notes for Skylar Compliance MR20251203 which updates the user interface of the "Upload Registration File" and "Manual Upgrade" modals to display a link to the new support site, where you can upload appliance keys and receive the associated update file. Added release notes for the Skylar Compliance SyncPack version 3.0.0, which rebrands the SyncPack to Skylar Compliance, adds the "Skylar Compliance: Pre Check" application, adds and updates multiple steps across multiple applications, and addresses multiple issues. Added release notes for the Skylar Compliance PowerPack version 107, which rebrands the PowerPack to the "Skylar Compliance" PowerPack.Skylar Compliance v3.0.0 SyncPack and Skylar Compliance v107 PowerPack are released
Hello, We are pleased to announce the release of the Skylar Compliance (formerly Restorepoint) v3.0.0 SyncPack and the associated Skylar Compliance v107 PowerPack. These releases contain many important updates, detailed here and in the Release Notes. With this release, ScienceLogic has rebranded the "Restorepoint" SyncPack to the "Skylar Compliance" SyncPack. You will notice this rebranding throughout the SyncPack, along with the Skylar Automation (formerly PowerFlow) platform. This change, as well as similar branding changes to the other products offered by ScienceLogic, reflects ScienceLogic's commitment to delivering intelligence that accelerates outcomes through service-centric observability, AI-driven operations, and intelligent automation. For more information, see the ScienceLogic website (https://sciencelogic.com/platform/overview) Features Included Updated the "CreateSkylarComplianceDevice" step to improve device creation and onboarding in the following ways: Updated plug-in retrieval to ensure the latest plug-in data is fetched, which will improve configuration of device backup protocols. Updated logic when preparing credentials to prevent duplicate creation of credentials. If a Skylar Compliance Device ID already exists for a device, it will not be created as a duplicate, and the Skylar One custom attribute will be updated." Updated the "Get Plugin Details" step to use real-time plug-in data. This ensures that whenever you update a device's configuration and/or protocols, you can log in to Skylar Compliance and adjust the default configuration of the plug-in. Subsequently, when a new device is registered, the real-time plug-in default configuration will be fetched, along with the protocol, enabling the creation of a new device using these updated details. Combined three of the steps in the "Skylar Compliance: Sync Devices" application into the "Retrieve Device Group Data from Skylar One" step to improve the efficiency of the process when retrieving devices under the "Skylar Compliance Devices" group and fetching the device limit from Skylar Compliance. Combined multiple steps of the "Skylar Compliance: Sync Devices" application into the "CreateandValidateCustomAttribute" step to allow a custom attribute to be created for a device if one does not exist. Additionally, added logging if a custom attribute already exists for a device. Added the "Skylar Compliance: Pre Check Application" Application, which runs a series of checks against Skylar Compliance (to ensure successful authentication and capacity) and Skylar One (to ensure proper connectivity, permissions, and API access). Running the application generates a detailed report that outlines the system's health, checks authentication compatibility with both Skylar Compliance and Skylar One, and highlights any necessary actions to take before proceeding. Added the "Device Provisioning Report" step to the "Skylar Compliance: Onboard Device" application. This step compiles information from previous steps and generates a "Device Provisioning" report. Added the "Enrich Devices with Credentials data " step to the "Skylar Compliance: Onboard Device" application. This step fetches and validates credential data from Skylar One using the globally unique identifiers (GUIDs) of the associated credential. Devices with missing or invalid credentials are flagged for review, then the enriched data is passed to the next step in the Skylar Compliance onboarding workflow. Added the "Get Device Details" step to the "Skylar Compliance: Onboard Device" application. This step gathers relevant information for each device, such as device property details, linked credentials, device class information, and device collector group information. Added the "Get collector group from Skylar One" step to the "Skylar Compliance: Onboard Device" application. This step fetches Data Collector information responsible for mapping agents in Skylar Compliance. Report data will now be generated when creating devices, both when a device failed to be created and when a device is successfully created. Updated the logic used when finding the Skylar Compliance domain and mapping it to a new device. Improved security when transferring data from one application step to another, such as transferring credential information. Added the "Skylar Compliance: Create or Update Custom Links" application, to allow for the creation and update of custom links for devices in Skylar Compliance. This application replaces functionality that was previously handled by the "Skylar Compliance: Sync Devices" application. NOTE: In order to successfully use the "Skylar Compliance: Create or Update Custom Links" application, you must set the "create_custom_link" configuration option value to zero in the "Skylar Compliance: Sync Devices" application before running the new application. Issues Addressed The following issues were addressed in this release: Addressed an issue with the "Skylar Compliance: Onboard Device" application that caused an error to be generated due to the default assignment of values from the SyncPack. (Cases: 00523695, 00527168) Addressed an issue that prevented Skylar Automation from successfully accessing the Skylar Compliance API. As a part of the fix for this issue, Skylar Automation will now check the HTTP response code during the "GetSkylarComplianceLicenseDetails" step, and will raise a "StepFailedException" error if a "401 - Unauthorized error" message is received. (Case: 00500459) Thank you, Release ManagementWe’re hosting a live AMA on r/sysadmin about the future of IT operations, join us!
Hi everyone — tomorrow we’re opening up a two-hour AMA focused on real-world IT operations: the challenges you’re facing today, the shifts coming with automation and AI, and what modern observability looks like as environments keep getting more complex. We’d love for you to join us at noon, Eastern, Thursday, Dec 4 here: https://www.reddit.com/r/sysadmin/comments/1pd8den/we_work_on_observability_and_automation_at/ You’re the experts running ScienceLogic in the wild and we’d love to hear your voice as part of the conversation. It will be interesting to hear from the broader sysadmin community which includes more than two million subreddit members. We expect to see the full range of ops experience levels, complexity and scale, large streamlined monitoring teams, and admin armies of one. Swing by and say hello, we look forward to seeing you there. And of course, Jared and I took AMA selfies.Net-SNMP Base Pack v104 PowerPack Release Notification
We are pleased to announce that the Net-SNMP Base Pack v104 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZUYCA4/netsnmp-base-pack Enhancements and Issues Addressed The following changes are included in this release: Resolved an issue where the “Net-SNMP CPU” and “Net-SNMP Physical Memory” Dynamic Applications would return PHP errors in logs by updating both Dynamic Applications to meet PHP 8 compatibility standards. Please refer to the Net-SNMP Base Pack v104 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Net-SNMP Base Pack v104 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Net-SNMP Base Pack v104 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Net-SNMP Base Pack v104 PowerPack Release can be found in the Release Notes.ScienceLogic Team observing US Holiday Thanksgiving- Nov 27th & 28th
Hello Nexus Community Members, Just a note that the SL team is observing the US Holiday Thanksgiving today and tomorrow. Our Product Managers & Subject Matter Expert's (SME's) will be back online on Monday. Thank you for all of your great participation, I really enjoy seeing the discussions going on. There is so much great information, best practices and ideas being shared amongst our customers and employees. Best Regards, Sara
