Ansible or Curl example for importing policy variables via API
Hello All, I'm trying to import a list of variables in to Restorepoint via the API "/policies/variables/import" with ansible but as of now I have no luck. Does anyone have an example (can be with Curl or another language) about the right syntax? Regards, MichaelSolved127Views1like4CommentsIntroducing the New ScienceLogic AI Platform – ScienceLogic's Next Era in Observability, Automation, and AI
At Nexus Live on October 8 th , we announced an important evolution of the ScienceLogic AI Platform: a new, unified naming convention under the Skylar™ name. This rebrand highlights our commitment to clarity and represents the investments we’ve made to deliver an industry-leading observability platform powered by visionary AI technology. What’s Changing The ScienceLogic AI Platform offerings are now: Skylar One (formerly SL1) Skylar Compliance (formerly Restorepoint) Skylar Automation (formerly PowerFlow) Skylar AI: Analytics (no change) Skylar AI: Advisor (no change) Skylar AI: Automated RCA will be retired as a standalone offering. Its capabilities will be integrated into upcoming Skylar Advisor releases, simplifying our offering for customers and providing broader and more powerful capabilities. Why This Change Matters Over the past 20+ years, ScienceLogic has continuously innovated and expanded through strategic investments and acquisitions. By consolidating our best-in-class offerings under the Skylar name, we: Simplifying our naming, reducing customer and market confusion Reflect tighter interoperability across products Deliver a more seamless, AI-driven experience This platform rebrand is about clarity, scale, and our long-term commitment to accelerating AI-led transformation. What to Expect Next You’ll start seeing Skylar naming convention across our website, content, Nexus Community, customer portal, products, and communications. Supporting resources, including documentation, certifications, training, and knowledge base articles, will be updated over time, aligned with product releases and version retirements, to minimize disruption. Need Help? For more details, please visit the Press Release and Skylar Renaming Page or reach out to your account team We’re excited to bring you along on this next chapter in our journey. The ScienceLogic Team View a special message from Dave Link and Douglas James.96Views2likes0CommentsSkylar 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 Management16Views1like0CommentsSkylar Compliance MR 5.6 20251022 Released
Hello - We are pleased to announce the release of Skylar Compliance 5.6 20251022, which was shipped to appliances that allow online updates today. NOTE: Restorepoint has undergone a corporate rebrand and is now known as Skylar Compliance. Going forward, these maintenance release notes will document the most recent updates for Skylar Compliance 5.6. Improved the Skylar Compliance Support Server to enhance operational security and communication with appliances. Renamed the ObjectName field to DeviceName on the Configuration Changes Summary report (Report > Add). Addressed an issue which prevented backups and command tasks from running and caused the Backup Now process to hang and to display a Loading message. (Case 00556250) Addressed an issue that caused a Disk is Full error message and prevented users from viewing Device Control outputs. (Case: 00565908) Addressed an issues that caused device plug-in fields, including credential fields, to clear when the Device page loaded. (Cases: 00562307, 00562318, 00562338) Thank you, Release Management16Views0likes0CommentsSkylar 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 Management13Views1like0Comments