Group Content
Recent Content
ScienceLogic: Geographic Maps v100 PowerPack Release Notification
We are pleased to announce that the first ScienceLogic: Geographic Maps v100 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/aBuVL000000169p0AA/sciencelogic-geographic-maps Description This PowerPack supports two functions vital for the use of Geographic Maps: A report to extract device and any existing location data. The spreadsheet this report generates is updated by the user to add additional location data and align devices to locations (only devices aligned to locations can be included) on a Geographic Map. Provide ScienceLogic with statistics on Geographic Map usage from early adopters that will help confirm the direction of future versions. PLEASE NOTE: A DRAFT Geographic Maps manual has been added to the portal for customer use. This is part of the main MAPS manual and is expected to be replaced by the entire MAPS manual in October. Please refer to the ScienceLogic: Geographic Maps v100 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the ScienceLogic: Geographic Maps v100 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The ScienceLogic: Geographic Maps v100 PowerPack Release File Details also contains links to the PowerPack Info Report.PowerFlow & PFCTL Updates
Hello - We have recently added the following versions of PowerFlow and PFCTL to the Support Portal: PowerFlow version 3.1.1 PFCTL version 2.7.11 Please use these versions for customers who are upgrading. The following versions are deprecated, as they contain minor issues that will interfere with satisfactory use of the products. If you have installed either of these release builds, we ask that you upgrade to the newest versions: PowerFlow version 3.1.0 PFCTL version 2.7.10 Thank you, Release ManagementSL1 PowerFlow v3.2.0 & PFCTL v2.8.0 Release
Hello, We are pleased to announce the release of SL1 PowerFlow v3.2.0, as well as the release of SL1 PowerFlow powerflowcontrol (pfctl) command-line utility v2.8.0. Both of these releases are included on the customer portal for download under Product Downloads > PowerFlow Platform > SL1 - PowerFlow 3.2.0. SL1 PowerFlow v3.2.0 adds the ability to bulk download reports, adds a new API endpoint to support bulk downloading of reports, adds two new configuration options to the docker-compose.yml file, and addresses multiple issues. Read on for more details or see the SL1 PowerFlow Release Notes. SL1 PowerFlow powerflowcontrol (pfctl) command-line utility v2.8.0 updates Couchbase-related checks, updates pfctl checks to require HTTPS certificates, and updates the pfctl init-sps action to use the HOST_ ADDRESS for the PowerFlow system. See the SL1 PowerFlow powerflowcontrol (pfctl) command-line utility v2.8.0 Release Notes. Features (SL1 PowerFlow v3.2.0) This section covers the features that are included in SL1 PowerFlow Platform version 3.2.0: You can now bulk download reports in PowerFlow. When bulk downloading, you have the option to select multiple specific instances of a report to download, or you can select all available instances to download. Added the new DELETE/api/v1/reports/batch API endpoint, which allows you to delete reports in a batch. For more details about using the new endpoint, see the API documentation in the PowerFlow user interface. Added two new configuration options to the docker-compose.yml file to allow access to the Couchbase and RabbitMQ user interfaces without requiring Dex authentication: DISABLE_DEX_AUTH. This option allows you to disable Dex authentication for the Couchbase and RabbitMQ services. ENABLE_SECONDARY_CB_UI. This option allows you to access the Couchbase user interface on port 8091 through secondary nodes without additional port openings. NOTE: The DISABLE_DEX_AUTH and ENABLE_SECONDARY_CB_UI configuration options are intended only for troubleshooting and should be turned off when the PowerFlow system is stable. Blank spaces in configuration options or application variables are now automatically stripped by the PowerFlow API to prevent the spaces from causing issues when PowerFlow reads the values. Updated API service initialization messages to improve clarity when Couchbase indexes are created. Updated the db_host configuration option to function more uniformly across all PowerFlow services. The following images are included in this release of PowerFlow: registry.scilo.tools/sciencelogic/pf-api:rhel3.2.0 registry.scilo.tools/sciencelogic/pf-couchbase:6.6.0-14 registry.scilo.tools/sciencelogic/pf-dex:2.37.1-11 registry.scilo.tools/sciencelogic/pf-worker:rhel3.2.0 registry.scilo.tools/sciencelogic/pf-gui:3.2.0 registry.scilo.tools/sciencelogic/pf-pypi:6.3.1-15 registry.scilo.tools/sciencelogic/pf-rabbit:3.8.35-7 registry.scilo.tools/sciencelogic/pf-redis:6.2.14-6 Issues Addressed (SL1 PowerFlow v3.2.0) The following issues were addressed in this release: Addressed an issue that caused device sync to fail due to region-specific cache key issues. (Case: 00422286) Addressed an issue that caused intermittent authentication failure when using SSO credentials to access PowerFlow. (Case: 00352925) Addressed an issue that caused the pfctl utility to fail when changing the PowerFlow password if the "dollar-sign" character ($) was used in the new password. You can now use the $ character in the PowerFlow password. (Case:00484230) Updated custom mappings values so that you can set any value you want before PowerFlow checks whether the value is unique. Previously, if you attempted to add a custom value and any part of the string matched an existing custom value, you could not attempt to save the value. Addressed an issue that prevented users with view-only permissions from accepting the End User License Agreement (EULA). Additionally, we have released SL1 PowerFlow System Utils v1.2.1 SyncPack today. This release is available on the customer portal here. This SyncPack requires the Base Steps SyncPack. Thank you, Release Management
SL1 Ibiza 12.3.7 Release Notification
We are pleased to announce that SL1 Ibiza 12.3.7 is now available. SL1 Ibiza 12.3.7 includes new features and enhancements in the following product areas: Agent Credentials Platform and Security Skylar AI System Update SL1 Ibiza 12.3.7 addresses issues in the following product areas: Data Collection and Retention Events and Alerts The release and documentation can be accessed using the following links: Ibiza 12.3.7 ISO Ibiza 12.3.7 Patch **Images will be announced early next week, and once available can be obtained from the support portal as well. For full details, see the SL1 Ibiza 12.3.7 Documentation: 12.3.7 Release Notes 12.3.7 Product Changes 12.3.7 Getting Started Guide Thank you, Release ManagementMicrosoft Teams v2.0.1 SyncPack is Released
Hello, We are pleased to announce the release of Microsoft Teams v2.0.1 SyncPack. The following issue was addressed in this release: Addressed an issue that prevented configuration objects from being visible after installing the SyncPack. (Case: 00559847) Thank you, Release ManagementAP2 Release Lokma
We're happy to announce that AP2 Lokma release (8.20.70-45) is now available! This release includes: The ability to set the refresh interval for services in bulk on the Business Services page Enhanced data handling and visibility on the Devices page Improvements to the Event Policy Editor Plus several additional new features and enhancements Please see the associated Release Notes for more information on these and other changes found in this release. You can download Lokma and associated release notes following this link: https://support.sciencelogic.com/s/release-file/aBtVL0000000zt70AA/lokmaRestorepoint 5.6 20250618 Release
Hello, We are pleased to announce the Restorepoint 5.6 20250618 release, which was pushed to Restorepoint appliances today. This release contains the following updates: Added the following options to the Request Settings pane (Administration > System Settings > Security tab) to allow you to configure the maximum body size for requests. These new option enhance system security: Max body size (in MB)- Sets the maximum requests for body size for all requests. Max file size (in MB)- Sets the maximum file size for requests that upload files. Updated the Alerts settings on the Logs/Alerts tab so the Email From field value is always prefixed with the "no-reply" username to ensure that users can only alter the domain name that Restorepoint will use to send email. Updated the Security page (Administration > System Settings > Security tab) to include the SSH Keys pane so you can upload or generate new appliance SSH keys. Added the following plugin updates in the Restorepoint user interface: Device details now show default plugin options if those options appear in the DefaultData for a plugin. Device configuration types (Devices > Edit Device > Configurations) that are configured as defaults in the plugin now appear with a preselected checkbox. The default Backup Port field on the Connection tab (Devices > Edit Device > Connection) uses the default port for the plugin unless it does not exist. If the default port does not exist, you can use the default port value for the protocol, which is shown as a placeholder when the Backup Port field is empty. (Case: 00517698) Updated the Create Agent API to include an Address field. Updated the Global Search user interface so the default value for the LimitVersion field displays "Last Version". This update also applies to the LimitVersion drop-down menu and the default "Last Version" is displayed when the LimitVersions field is omitted in the API. Addressed an issue that caused an error message to appear when users with limited access opened the View Device Configuration page. (Case: 00521451) Thank you, Release ManagementVMWare: vSphere Base Pack v309 PowerPack Release Notification
We are pleased to announce that the VMWare: vSphere Base Pack v309 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/aBu0z000000XZeiCAG/vmware-vsphere-base-pack The following enhancements and addressed issues are included this release of the VMWare: vSphere Base Pack v309 PowerPack: As of version 309 of the PowerPack, you can now define whether to require SSL verification. The VMware credential now includes a CURL option called "SSLVERIFYPEER" which allows you to configure whether to skip or require verification. As of version 309, the PowerPack no longer supports VMware versions below 7.0. Added support for discovery of Template and VirtualMachine folders to the PowerPack. Added DCM+R support for Virtual Machine to Windows Server devices. Added Component Availability Identifier to the "Unique Id" collection object in the "VMware: NetworkFolder Network Discovery" Dynamic Application in order to correctly reflect the availability status of the network. When networks are removed, their status will now correctly update to "Unavailable" and they will vanish according to vanishing settings. (Support Case: 00433671) Addressed an issue that caused a "-1" value to be returned for a performance metric. The fix correctly handles "-1" as NO DATA in performance Dynamic Applications. (Support Case: 00434633) Addressed an issue with the "Vmware: Datastore Storage Performance" Dynamic Application that caused "NoneType" errors when processing lists. (Support Case: 00416987) Addressed an issue that prevented device information from updating properly after upgrading to version 308 of the PowerPack. (Support Case: 00402298) VM Snapshots created by third-party tools would sometimes be missing data such as age (creation time) or size. Those configurations are now supported. (Support Case: 00363112) Addressed an issue with the "Vmware: VirtualMachine Configuration" Dynamic Application that prevented VM Snapshots from updating correctly. (Support Case: 00397489) The collector affinity of "VMware: HostSystem Memory Performance" Dynamic Application has been changed to root affinity, as it requires cache data only available on the root collector. (Support Case: 00431040) Removed the "other" option from the "Vmware: Events" snippet. (Support Case: 00370913) Addressed an issue that caused the VMware credential tester to fail when it should not. Note: This issue is addressed for version 12.2.0+ of SL1. VMware PowerPacks running on version 11.3-12.1.x will still be unable to run the credential test. Addressed an issue that prevented the "Virtual Disk Average Read Latency" and "Virtual Disk Average Write Latency" metrics in the "VMware: Datastore Cluster Storage Performance" Dynamic Application from collecting data. Addressed an issue that caused the "VMware: Component Count Config" Dynamic Application to fail. Addressed an issue that caused the "Vmware: VirtualMachine IC UpTime" Dynamic Application to trigger notice events in the system logs. Addressed an issue that caused the "Vmware: VirtualMachine Configuration" Dynamic Application to discover a false snapshot that shared a name with the virtual machine and contained no other information. Addressed an issue that prevented a Virtual Machine configuration from updating to reflect the additional available data if VMware Tools is activated or deactivated on a Virtual Machine. Please refer to the VMWare: vSphere Base Pack v309 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the VMWare: vSphere Base Pack v309 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The VMWare: vSphere Base Pack v309 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the VMWare: vSphere Base Pack v309 PowerPack Release can be found in the Release Notes.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 ManagementCisco: Meraki API v115 Py3 PowerPack Release Notification
Meraki v115 was pulled from the portal and is being replaced by Meraki v115.1 on 10/13/25 We are pleased to announce that the Cisco: Meraki API v115 Py3 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/aBu0z000000XZRPCA4/cisco-meraki-api Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Added a universal credential and guided discovery workflow to the PowerPack. The universal credential includes configuration options for SSL certificate verification, proxy configuration, and selective discovery. For more information on configuring a Cisco Meraki universal credential, see the "Creating a Universal Credential for Cisco Meraki" section in the Cisco: Meraki [API] PowerPack manual. Added support for SSL certificate verification to the SOAP/XML and universal credential types. Added support for selective API endpoint collection to the SOAP/XML credential type, which allows you to define specific API endpoints to exclude from collection. For more information on configuring selective API endpoint collection, see the "Creating a SOAP/XML Credential for Cisco Meraki" section in the Cisco: Meraki [API] PowerPack manual. Added new fields to the universal credential type to enable retry override capability: Maximum number of retries Time between retries NOTE: These credential headers and fields should only be changed for troubleshooting purposes. Changing these values can cause collections to take longer to run, which could result in missing data or early termination (sigterm). Updated the names of the example credentials in the PowerPack to the following: Cisco: Meraki - API Basic Example Cisco: Meraki - API Example (Selective) Cisco: Meraki - API Proxy Example Cisco: Meraki - API Example Removed the "Discovery" collection object from the "Cisco: Meraki Organization Discovery [API]" Dynamic Application. Added the new "Cisco: Meraki Wireless Stats [API]" Dynamic Application, which allows you to collect information for wireless Cisco Meraki devices. NOTE: This Dynamic Application is disabled by default, and must be manually aligned to Cisco Meraki devices. For information about configuring the "Cisco: Meraki Wireless Stats [API]" Dynamic Application, see the Cisco: Meraki [API] manual. Added the new "Cisco: Meraki AP Utilization Performance [API]" Dynamic Application, which you can use to collect information on wireless access point (WAP) type devices. NOTE: This Dynamic Application is disabled by default. For information about configuring the "Cisco: Meraki AP Utilization Performance [API]" Dynamic Application, see the Cisco: Meraki [API] manual. Updated the "Cisco: Meraki Device Discovery [API]" Dynamic Application so that a device's MAC address is assigned as the device name instead of its serial number when no name is assigned. If you want to update the name of the device manually, you must disable the "Preserve Hostname" option on the device. Updated the alert formulas for both alerts in the "Cisco: Meraki Uplink Status [API]" Dynamic Application so that alerts and events are only generated when the status changes from "Active/Ready" to "Disabled/Not Connected". Updated the "Cisco: Meraki Uplink Performance [API]" Dynamic Application to index data by destination IP, which addresses issues with multiple IP configurations in Cisco Meraki. As part of the updates, the alert names for the "Cisco: Meraki Uplink Performance [API]" have been updated to reflect accurate conditions and include the specific IP. Added three new collection objects to the "Cisco: Meraki Request Manager [API]" Dynamic Application to display information on skipped endpoints. Added the new "Cisco: Meraki [API] Py3" Execution Environment, which is compatible with Python 3. NOTE: ScienceLogic recommends removing the "Cisco: Meraki [API]" execution environment after upgrading to version 115 of the PowerPack. Added logging for the "Cisco: Meraki Org Write [API]" run book action policy and included the run book action status in the "Event Log Action" entry for the run book action policy. Addressed an issue with the "Cisco: Meraki Uplink Usage Performance [API]" Dynamic Application that caused incorrect percentages to display for the "Uplink - Download Utilization Percent" and "Uplink - Upload Utilization Percent" presentation objects. (Case: 00428304) Please refer to the Cisco: Meraki API v115 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: Meraki API v115 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: Meraki API v115 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: Meraki API v115 Py3 PowerPack Release can be found in the Release NotesWindows_PowerShell_Automations_v105_Py3 PowerPack Release Notification
We are pleased to announce that the Windows_PowerShell_Automations_v105_Py3 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/aBu0z000000XZgoCAG/windows-powershell-automation Enhancements and Issues Addressed This release includes the following features: Added a new Python 3.6 Execution Environment called "Windows PowerShell Automations v2.0" and updated the libraries for Python 3.6 compatibility. Updated the action type snippet code for Python 3.6 compatibility. Added the following run book automation policies to this PowerPack, and set the Policy Type for each to Active Events/User Initiated: Windows PowerShell: Run CPU & Memory Diagnostic Commands Windows PowerShell: Run CPU Diagnostic Commands Windows PowerShell: Run Disk I/O Diagnostic Commands Windows PowerShell: Run Disk Usage Diagnostic Commands Windows PowerShell: Run Memory Diagnostic Commands Windows PowerShell: Run Print Job Error Diagnostic Commands Please refer to the Windows_PowerShell_Automations_v105_Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Windows_PowerShell_Automations_v105_Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Windows_PowerShell_Automations_v105_Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Windows_PowerShell_Automations_v105_Py3 PowerPack Release can be found in the Release NotesAP2 release IcePop
We're happy to announce that AP2 IcePop release (8.17.23.18) is now available! This release includes improvements to the Service Policy tab of the Service Investigator page, service policy management from the Edit Service Policy page; additional bulk actions on the Devices page and better visibility of event data on the Device Investigator. Please see the associated Release Notes for more information on these and other changes found in this release. You can download IcePop and associated release notes following this link: https://support.sciencelogic.com/s/release-file/aBtVL0000000inR0AQ/icepopSL1 Hollywood 12.2.4 Release Notification
We are pleased to announce that SL1 Hollywood 12.2.4 is now available. The release and documentation can be accessed using the following link: https://support.sciencelogic.com/s/release-file/aBtVL0000000TbV0AU/1224 The release contains enhancement in Logging and Security updates, and updates in Credentials, Data Collection and Retention, Device Management, Discovery, Events, Monitoring Policies, System Update, and Topology If you are planning to consume SL1 Hollywood 12.2.4, be advised of the following: This release is available only as a patch; there is no ISO version. You can upgrade to 12.2.4 directly from the following SL1 versions: 12.1.2, if all SL1 appliances are running on Oracle Linux 8 (OL8) 12.2.1.1 12.2.1.2 12.2.3 If you are currently on SL1 12.1.0.2 or 12.1.1 and all of your appliances are running on Oracle Linux 8 (OL8), you can upgrade to 12.1.2 or 12.2.1.2 and then to 12.2.4. STIG-compliant users can upgrade to 12.2.4. You must currently be on a version of SL1 with all appliances running on Oracle Linux 8 (OL8) before you can upgrade to 12.2.4. AWS deployments that are using Aurora 3 cannot upgrade to 12.2.4. Users who currently use Python 3.9 execution environments for Dynamic Applications and Run Book Automations should not upgrade to 12.2.4. Due to a known issue, Python 3.9 is not supported in this release. A fix for this issue is planned for version 12.2.5. After upgrading to 12.2.4 and running a security scanning tool against your SL1 appliances, you might experience an issue where the scan lists several "Oracle Linux 8 : container-tools" ELSA security findings. This is due to a known issue that is preventing SL1 from removing certain unneeded packages during the upgrade process for this release. If this occurs, you must perform a manual workaround to remove those packages. For full details, please see the SL1 Hollywood 12.2.4 release notes: https://docs.sciencelogic.com/release_notes/sciencelogic_12-2-4_release_notes.pdfAP2 release Halwa
We're happy to announce that AP2 Halwa release (8.16.1.14) is now available! This release includes enhancements to the Timeline panel on the Service Investigator page, a new Device Groups widget on Dashboards, Improved data visibility and management on the Devices page, Improved event management on the Events page, an updated GraphiQL browser user interface, and enhancements in Credentials and Global Manager. Please see the associated Release Notes for more information on these and other changes found in this release. You can download Halwa and associated release notes following this link: https://support.sciencelogic.com/s/release-file/aBtVL0000000TV30AM/halwaCisco Cloud Center and Cloud Center Suite PowerPacks moving to EOL
As of 8/12/2024, download access for the Cisco: Cloud Center and Cisco: Cloud Center Suite powerpacks is being restricted on the product download portal as these integrations are “End of Life” status. These PowerPacks were previously “End of Maintenance”
About Product Release Notifications
This user group is for Product Release Notifications
Open Group