Skylar Compliance 5.6 20251119 is Released
Hello, We are pleased to announce the release of Skylar Compliance 5.6 20251119 for appliances. This release contains important updates including the following: Restorepoint is now Skylar Compliance. With this release, ScienceLogic has rebranded Restorepoint to Skylar Compliance. You will notice this rebranding throughout the platform. This release focuses on user interface reskinning and labeling changes to match the new Skylar brand, while core functionality remains unchanged. 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). IMPORTANT: Specific actions are required to view the rebranding changes. Please follow the instructions for your appliance settings. Online appliances with auto updates ON. No manual update action is needed, however, you must clear your browser cache to see the new branding changes. Online appliances with auto updates OFF. You must apply the update manually and then clear your browser cache to see the new branding changes. Offline appliances. You must update through your offline process and then clear your browser cache to see the new branding changes. Bulk updating the Vrf field for devices now functions as intended, and the changes are saved properly for all updated devices. (Case: 00568480) Addressed an issue with the user interface that caused plug-in credential fields on the [Connection] tab to reset when loading a device page with specific plug-ins. (Case: 00577088) Addressed an issue that prevented successful comparison of backups due to changes in the backup manifest file types and plug-in updates. (Case: 00567986) Addressed an issue that prevented large backups from being successfully uploaded to devices. (Case: 00577908) The following updates were released as part of the RPM Agent and are provided here as information only: Addressed an issue that caused backups not to fail correctly when the Disable SSH Strict Host Key Checking option was enabled. (Case: 00577892) Addressed an issue that caused an error to display in the agent logs when attempting to insert a job into the database. (Case: 00575046) Addressed an issue that prevented agents from updating properly and caused them to leave nonfunctioning processes behind during updates. (Case: 00574638) Please refer to the Release Notes for further information. Thank you, Release Management56Views2likes0CommentsSkylar Compliance RPM Agent v5.6 20251119 is Released
Hello, We are pleased to announce the release of Skylar Compliance RPM Agent version 5.6 20251119. This release contains the rebranding updates (see IMPORTANT below) and addresses multiple issues including Addressed an issue that caused an error to display in the agent logs when attempting to insert a job into the database. (Case: 00575046) Addressed an issue that caused backups to fail incorrectly when the "Disable SSH Strict Host Key Checking" option was enabled. (Case: 00577892) Addressed an issue that prevented agents from updating properly and caused them to leave nonfunctioning processes behind during updates. (Case: 00574638) IMPORTANT: Please note that this version of the RPM Agent is rebranded, using the Skylar Compliance product name. Specific actions are required to view the rebranding changes. Please follow the instructions for your appliance settings. Online appliances with auto updates ON. No manual update action is needed, however, you must clear your browser cache to see the new branding changes. Online appliances with auto updates OFF. You must apply the update manually and then clear your browser cache to see the new branding changes. Offline appliances. You must update through your offline process and then clear your browser cache to see the new branding changes Refer to the latest Release Notes for more information about the Agent and the appliance. Thank you, Release Management56Views2likes0CommentsRestorepoint
Restorepoint is a Disaster Recovery and Secure Configuration Management appliance for network devices such as routers, switches, proxies, and firewalls. Restorepoint can automatically retrieve your network device configurations, detect changes and compliance violations, and report these automatically to network administrators. In this Powerhour session we will share with you how to add devices into Restorepoint, why having backups collected is useful in an autonomic IT environment, and how to leverage the SL1 platform in support of key workflows. Additionally, we will present the benefits of Governance, Risk and Compliance (GRC). Within the ScienceLogic Network Change and Configuration Management (NCCM) platform you will be backup over 100 different types of network equipment including firewalls to a central repository. Once the backup is collected then you can track change over time for auditing purposes as well as day to day operational needs to manage effective change control. Integration to the monitoring and automation platform adds layers of value which we will discuss during our session. When your organization is tasked with managing GRC then Restorepoint will apply your rules to assist in real time awareness of compliance. When configuration drift occurs then an alert will be sent to the SL1 platform for execution of automations in support of your defined workflow. For instance if you need to collect the difference of the last two configurations to compare an unplanned change while opening an incident into your IT Service Management (ITSM) product that can be completed so your operations team only need to receive the enhanced information set and begin resolutions steps. Often the best step is to revert the change and of course that’s supported from SL1 to allow for reduction in your Mean Time to Repair (MTTR). At the end of the June PowerHour you will have learned how to add devices into Restorepoint, why having backups collected is valuable and how to leverage the SL1 platform in support of key workflows. Additionally, we will present the benefits of Governance, Risk and Compliance (GRC). While blending into the overall SL1 platforms workflow operational needs135Views1like0CommentsAccess to SL1 and RP AMI's to automate AWS Provisioning
We're in the process of developing pipelines to provision and configure all our resources in AWS on a per client basis. Among these resources are the SL1 collector and RP agent. Right now in order to request the AMI for SL1 we need to fill out the form at https://support.sciencelogic.com/s/request-amazon-ami after authenticating via the webpage. Because of the login flow this has proven difficult to pass through the right information to authenticate and access the AMI request form where we can pass the form data to request the AMI on our AWS account. I understand this is probably not a common case, but has anyone come across a way to accomplish anything similar? The best I've been able to do so far is use Selenium to manage a browser logging in and navigating to the form page, but it doesn't lend itself well to the pipelines. For RestorePoint it seems like we still need to submit a case and request the AMI from support. Is there any plans to add this to the same request form for the SL1 AMI's? For now we're alright sticking to the manual effort of requesting AMI's, but it would be nice to be able to click a button and be done with provisioning :).111Views1like0CommentsConfiguration Recovery - SL RestorePoint
Hello all, I just had this question posed to our team regarding config recovery. "Do you have any way of retrieving the configs for switches that have been deleted from SLRP please?" Is there a way to retrieve a backup of RestorePoint (and maybe restore to a temp location) from a specific point in time? If anyone has any advice or previous experience with this SL RestorePoint scenario, your input would be greatly appreciated!171Views1like2CommentsWe’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.53Views1like0CommentsSkylar Compliance 5.6 20251113 Release
Hello, Skylar Compliance released a hotfix for appliances today: Version 5.6 20251113. The following issue is fixed in this release: Addressed an issue that caused large backup uploads to fail with the error message "multipart:NextPart:http request body too large". (Case: 00577908) Thank you, Release Management54Views1like0CommentsSkylar Compliance 5.6 20251105 Release
Hello, Skylar Compliance 5.6 20251105 is released. The following update was provided for appliances: Addressed an issue that caused a memory leak for large reports, which caused out-of-memory issues. The report generation process was simplified. Thank you, Release Management59Views1like0CommentsThis week's updates to the Doc sites at docs.sciencelogic.com
8/29/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Added release notes forRestorepoint 5.6 MR 20250827, which addresses issues with the command scheduler for multi-device command schedules, addresses the Device Details scrolling issues; updated the default Regex buffer size to 5%; and migrated the Configure Changes report into the current user interface.51Views1like0Comments