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
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, SaraScienceLogic Leadership Interview with Dave Link and Douglas 'DJ' James
For years, SL1, PowerFlow, Restorepoint, and Skylar AI have powered IT operations through visibility, automation, compliance, and intelligence. Now, we are unifying these capabilities under the Skylar name as part of the ScienceLogic AI Platform. In this conversation, Dave Link and Douglas "DJ" James discuss what this change means for customers, how the platform has grown more integrated over time, and how unifying under the Skylar name reflects the new era of ScienceLogic.Learn more about Skylar Automation
Skylar Automation is ScienceLogic’s low-code/no-code automation and integration offering, orchestrating workflows across IT ecosystems at scale. It efficiently and seamlessly connects Skylar One data, signals, and insights with ITSM, DevOps, and cloud tools to enable closed-loop automation. It’s also sustainable, highly performant, and easy to maintain without requiring dedicated staff. Beyond simply unifying siloed systems and powering intelligent automation, Skylar Automation eliminates manual toil, improves efficiency, and helps organizations progress on their journey toward Autonomic IT.Learn More about Skylar One (formerly SL1)
Skylar One (formerly SL1) is ScienceLogic’s core observability offering, delivering unified visibility across hybrid and multi-vendor environments. Skylar One ingests and correlates telemetry data into business context, enabling intelligent automation and comprehensive observability. When deployed with Skylar Automation, Skylar One users benefit from deep integrations into ITSM platforms like ServiceNow, providing automated CMDB updates and incident workflows, reducing MTTR and improving resilience. Skylar One empowers enterprises to connect fragmented data silos, accelerate root cause analysis, and drive cost-optimized operations at scale.Skylar One Juneau: More Speed. Better Maps. Smarter Topology. Happier Weekends.
6 MIN READ When customers help guide the roadmap, the result looks a lot like Juneau (12.5.1). It’s practical, focused, and full of improvements you asked for. And while this version introduces new marquee features, Skylar One (SL1) customers are more likely to notice how it brings together hundreds of customer-driven engineering upgrades. The result is something admins, operators, and SREs will recognize instantly: a platform that runs faster, models the world more accurately, and fits easily into the rhythm of how you operate. With 700+ enhancements across ingestion, topology, eventing, collectors, HA, UX, and hardware support, Juneau is one of the most customer-driven releases we’ve delivered. These changes come straight from real deployments, break/fix pain points in the field, and hands-on sessions with SEs, Support, and Professional Services. And of course, huge thanks to the brilliant members of the Nexus User Community and all your contributions to the Nexus Idea Hub. Let’s dive into a few highlights from Juneau. A Platform That Feels Faster (Because It Is) Juneau’s performance improvements aren’t theoretical. The ingestion and data processing pipelines now move up to 60% more throughput, thanks to extensive tuning and backend re-architecture. In large environments, this directly translates into smoother dashboards, more up-to-date metrics, and fewer ingestion bottlenecks under unusually heavy load. Daily data maintenance was also rebuilt to use far less CPU and I/O, eliminating one of the most common sources of delay during maintenance windows. For large deployments, this means more predictable performance and smother scaling to peak load. In short: the system breathes easier. And as you already know, when goto ops tools run faster, the entire operational experience improves. Topology That Matches the Networks You Run Topology modeling has always been one of SL1’s superpowers and Juneau gives it a serious upgrade. LLDP and CDP relationship extraction got a ground-up refresh. One of the most impactful changes: LLDP now forms multiple valid relationships across interface pairs instead of aggregating them into one. Bonded links, trunk groups, and redundant uplinks now show up exactly as they exist in the environment. Similarly, topology can now form relationships even when only one side of the connection reports neighbors. For environments with asymmetric discovery policies, strict security controls, or devices that don’t speak every discovery protocol, this is a major practical improvement. You now get a more complete graph, even when the inputs are less than perfect. Add in new global controls for per-protocol behavior, and discovery becomes far more adaptable to the real world — not just an ideal one. Geographic Maps: A New Operational Lens Juneau introduces Geographic Maps as a new data & visualization type, and a new dimension to operational awareness. You can now visualize devices, services, and health states geographically across regions, campuses, data centers, cloud footprints, retail branches, or industrial sites. Here are just a few customer use cases: MSPs validating customer regions Retailers preventing brick-and-mortar outages Energy and utilities tracking state-level impact Distributed enterprises troubleshooting local vs. regional issues And many more… Skylar One Geographic Maps isn’t simply NOC bling — it’s a diagnostic tool. Geographic Maps surface real-world patterns that don’t always fit neatly into lists or dashboards. They make regional correlation simple. And even better, they turbocharge understanding for business services and synthetics. We can’t wait to see how you’ll take advantage of geo-aware data and visualization. And yes, automatically zooming, context-aware, full-screen Global Ops maps do make for sparkly NOC bling. Event Policy Editor: Redesigned by You Juneau includes a new Event Policy Editor that streamlines the configuration and optimization for event policies based on your feedback. The new UI is cleaner with an optimized layout and validates changes in real time. It’s easier to ensure accuracy, faster to build policies, and easy for new admins to learn. Business Service policy tuning also benefits from the same treatment, with clearer rule logic and intuitive metric selection. If you manage complex event pipelines or regularly onboard new operators, this is a quality-of-life upgrade you’ll notice immediately. AI Observability from Model to Metal (Now with AMD GPUs) Believe it or not, self-managed AI infrastructure isn’t niche anymore — it’s becoming core to how advanced operations teams ensure tight AI security and cut cloud opex. Juneau expands Skylar One’s existing NVIDIA GPU and LLM workload monitoring to include full AMD GPU visibility, completing true model-to-metal observability. You get insight into GPU temperature, utilization, memory pressure, power draw, error states, and other AMD-specific signals, all stitched into the same service context that already connects your models, inference endpoints, OS behavior, and chassis health. For teams managing AI platforms, this is welcome news. For example, you can now measure the relative efficiency of specific AI workloads across different combinations of datacenter components and recommend the most cost-effective mix to maximize LLM performance for your operations. If you’re running LLM inference nodes, GPU training clusters, HPC pipelines, or any data-intensive workloads, this enhancement further extends the ScienceLogic AI Platform’s comprehensive observability. Skylar One now interprets the entire AI stack as a single, coherent system — from model behavior to GPU thermals to the infrastructure beneath it. It’s the same level of intelligent, correlated insight you expect for CPUs, networks, containers, storage, cloud, and more, now fluent in even more of the most performance-sensitive workloads you operate. Synthetics Become a First-Class Citizen in Juneau For a long time, synthetic tests in Skylar One were powerful but lived a little off to the side. They were easy enough to integrate but not fully woven into workflow. With Juneau, synthetics become a first-class citizen in Skylar One. Recording a synthetic transaction now feels familiar to anyone who’s used a modern DEM tool: record an application workflow in a browser via Playwright Codegen, drop the generated Playwright script into a Skylar One dynamic app, assign a credential, and you’re ready to test from multiple locations. Just record, point, click, run. But the real shift happens after you deploy synthetic tests. Because they’re now fully integrated into Skylar One, real-world application performance shows up everywhere operators already live — dashboards, business services, context panels, service health, and even Geographic Maps. Multi-location failures become much easier to troubleshoot when you have quantifiable experience data from an end-user perspective. And yes: Skylar One still works seamlessly with your existing DEM, RUM, and APM investments. If you rely on browser-based monitoring from Dynatrace, New Relic, AppDynamics, or others, Skylar One can continuously ingest and contextualize those signals too. But with the Juneau release, external tools are no longer required. Synthetic visibility is built in and part of the core platform experience. For teams who depend on predictable user journeys, distributed site uptime, or multi-step workflows, synthetics in Juneau aren’t just easier to run. They’re now part of the operational heartbeat of Skylar One. High Availability, Low Maintenance Some improvements don’t need a spotlight — they just work the way you expect. Improvements to High Availability is a perfect example. If you’ve ever stared at any application during failover and quietly wondered, “Is it switching… or just thinking about it?”, you’ll appreciate Juneau’s enhancements to Skylar One’s High Availability. This release tightens the entire HA failover path. Link-state detection is faster and more accurate (especially in environments without crossover links). Heartbeat monitoring is more responsive. Cluster state transitions settle quickly. And the updated logic avoids unnecessary retries that slowed down election decisions in some configurations. The result is HA that kicks in quickly, transitions reliably, and behaves with the no-fuss confidence you expect from tier-1 enterprise platforms. Python 3 Everywhere: Faster, Safer, and Ready for What’s Next The Juneau release completes Skylar One’s transition to a pure Python 3 platform. Collectors, platform services, dynamic apps, extensions — everything now runs on a single, modern runtime with no legacy paths or dual execution. Python 3 is industry standard for good reasons. It’s faster, more secure, and far better supported by modern libraries and tooling. Moving to a single runtime improves workload performance, strengthens security posture across the platform, and simplifies everything from dynamic app development to upgrades and long-term maintenance. Deprecated Python 2 powerpacks are clearly indicated in the admin UI so teams can identify and update any remaining artifacts with ease. Skylar One Juneau — Ready for You, Ready for Anything Juneau brings meaningful improvements across the features of Skylar One that operators depend on most. Faster ingestion, sharper topology, integrated synthetics, Geographic Maps, streamlined HA, full-stack AI observability, and a fully modern Python foundation come together in a release that’s more capable, more responsive, and more aligned with how your team works. It was engineered with customer input at its core, RC tested in user environments, and ready to support the next wave of your AIOps workflows. Check out the Getting Started Guide for more details and documentation links. We can’t wait to get your feedback on the latest release from ScienceLogic.
This week's updates to docs.sciencelogic.com
11/21/25 Doc updates to the main docs site at https://docs.sciencelogic.com/: Updated the Geographic Maps chapter of the Maps manual to reflect the new version numbers for the script and configuration files, which are required for assigning location data to devices. 11/21/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/: Added release notes for the F5: BIG-IP v106 PowerPack which updates for Python 3.11 compatibility and event policy descriptions so they are more easily consumed by Skylar One. Added release notes for Cisco Base Pack v218, which include enhancements to Dynamic Application data collection, updated descriptions for Event Policies, and several issue resolutions. Added release notes for Skylar Compliance MR20251119 which addresses multiple issues and adds rebranding changes from Restorepoint to Skylar Compliance.
