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
Recent Content
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, MichaelJuniper Mist v100.1 PowerPack Release Notification
We are pleased to announce that the Juniper Mist v100.1 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/aBuVL0000000b1B0AQ/juniper-mist The following enhancements and addressed issues are included this release for Juniper Mist: Added support for collection using a proxy to the PowerPack. For more information about using a proxy, see the Juniper: Mist manual.. Added a divide by zero check to the "Memory Utilization" presentation object in the "Mist: AP Statistics" Dynamic Application. Please refer to the Juniper Mist v100.1 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Juniper Mist v100.1 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Juniper Mist v100.1 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Juniper Mist v100.1 PowerPack Release can be found in the Release NotesModify Link-Message in Event Policy
I've done some digging and so far haven't found a way to change the text in a Link-Message that's associated with an event policy. I know we can change the name of the policy itself but not to the text that's associated with it. The one I want to change is "161: Bandwidth usage exceeded threshold: %V". This is the message associated with the interface utilization threshold, and the word "bandwidth" in it is confusing some users. Is this something we can do?This week's updates to the Doc sites at docs.sciencelogic.com
1/31/25 Doc updates to the main docs site at https://docs.sciencelogic.com/ Updates to the Docker PowerPack manual to support changes from version 108 Updates to the HPE: Edge Connect (Silver Peak) PowerPack manual to support changes from version 200. 1/31/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Docker v108 PowerPack which updates the PowerPack to make it compatible with Python 3, addresses an issue with the "Docker: Host Device Class Realignment" run book action, and adds a device template to use if Dynamic Applications fail to align automatically during discovery. HPE: Edge Connect (Silver Peak) v200 PowerPack, which updates the PowerPack to Python 3, adds multiple Dynamic Applications, and adds a new example credential.HPE Edge Connect (Silver Peak) v200 Py3 PowerPack Release Notification
We are pleased to announce that the HPE Edge Connect v200 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/aBu0z000000XZaHCAW/hpe-edge-connect-silver-peak Enhancements and Issues Addressed: Updated the PowerPack to be compatible with Python 3 Converted all Dynamic Applications to Python 3. Added two new Dynamic Applications to the PowerPack: HPE: Edge Connect Appliance Memory Performance HPE: Edge Connect Appliance CPU Performance NOTE: Both of the "HPE: Edge Connect Appliance Memory Performance" and "HPE: Edge Connect Appliance CPU Performance" Dynamic Applications are disabled by default. Enabling the "HPE: Edge Connect Appliance CPU Performance" Dynamic Application may cause performance issues on the orchestrator due to the Dynamic Application calling the API for each appliance device. Removed the "REST: Performance Monitor" Dynamic Application from the PowerPack, as it is not compatible with the Snippet Framework. IMPORTANT: Before upgrading to version 200 of the PowerPack, ScienceLogic recommends unaligning the "REST: Performance Monitor" Dynamic Application from existing root virtual devices. Added the new "HPE: Edge Connect v200 API Key" UCF subtype to the PowerPack. Added the new "HPE: Edge Connect API Key Example (UCF)" example credential to the PowerPack. Added a function to the snippet of each Dynamic Application in the PowerPack that checks for an API token in the headers. If one is found, you will receive a warning that instructs you to move the token to the "Embedded Password [%P]" field. NOTE: ScienceLogic does not recommend storing tokens in plain text fields, as this goes against security best practices. Please refer to the HPE Edge Connect v200 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the HPE Edge Connect v200 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The HPE Edge Connect v200 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the HPE Edge Connect v200 Py3 PowerPack Release can be found in the Release Notes.Docker v108 Py3 PowerPack Release Notification
We are pleased to announce that the Docker v108 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/aBu0z000000XZalCAG/docker The following enhancements and addressed issues are included this release: Updated the PowerPack to be compatible with Python 3.6 (SOL-27653) Addressed an issue that caused the "Docker: Host Device Class Realignment" run book action to activate incorrectly in certain situations. As part of the fix for this issue: The "Docker: Hosts and Swarm Cluster realignment to CU id of the leader node" event policy will only be triggered by the leader node. If one or more nodes are not discovered, they will not be taken into account when deciding whether to trigger the event. The run book action now uses the IP address instead of the hostname to read the cache, because the cache is saved using the IP address. (Case: 00424553) (SOL-27032) Added the "Docker Template Example" device template that you can apply to root (Docker Host) Docker devices if the required Dynamic Applications fail to align automatically during discovery. (SOL-1427) Made several modifications to example credentials in the PowerPack. Please refer to the Docker v108 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Docker v108 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Docker v108 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Docker v108 Py3 PowerPack Release can be found in the Release Notes.Correction: F5: Big IP DNS v101 Py3 PowerPack Release Notification
F5: Big IP DNS v101 Py3 PowerPack Release Notification Correction on the DNS Link below to take you to the correct PP - F5: Big IP DNS We are pleased to announce that the F5: Big IP DNS v101 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/aBu0z000000XZOfCAO/f5-bigip-dns The following enhancements and addressed issues are included in this release of the"F5: BIG-IP DNS": Updated the PowerPack to be compatible with Python 3. Updated the PowerPack to support the BIG-IP 4800 device class and to ensure the correct device classification icon appears in the current user interface when viewing in the Device Manager and Device Properties pages. Addressed an issue that caused storage object failures in the "F5 BIG-IP DNS: Pool Configuration" and " F5 BIG-IP DNS: Pool Member Configuration" Dynamic Applications. (Case: 00344259) Updated the Collector Affinity for the Dynamic Applications to Root Device Collector for this PowerPack. Please refer to the F5: Big IP DNS v101 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the F5: Big IP DNS v101 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The F5: Big IP DNS v101 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the F5: Big IP DNS v101 Py3 PowerPack Release can be found in the Release Notes.This week's updates to the Doc sites at docs.sciencelogic.com
1/24/25 Doc updates to the main docs site at https://docs.sciencelogic.com/ SL1 PowerFlow manual updated with changes for PowerFlow version 3.1.0 and PowerFlow powerflowcontrol (pfctl) v2.7.10. Added updated snippet functions for import logging from a Dynamic Application or a run book snippet in the Run Book Automations manual. Added a new Upgrade Checklist and Upgrade Path Matrix for SL1 to the System Administration manual. AMPQ: RabbitMQ v103, which includes updates to support Python3 compatibility. F5: BIG-IP DNS v101, which includes updates to support Python3 compatibility. 1/24/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ SL1 PowerFlow v3.1.0, which addresses several issues and adds multiple user interface improvements for PowerFlow, including indicators for the number of schedules for an application, a persistent footer at the bottom of PowerFlow with system information, and an "Export to CSV" option for SyncPacks. SL1 PowerFlow powerflowcontrol (pfctl) v2.7.10, which includes multiple fixes and improvements for node and cluster actions. This version of the utility is included with the PowerFlow Platform version 3.1.0 release. AMPQ: RabbitMQ v103 PowerPack, which includes updates to support Python3 compatibility. F5: BIG-IP DNS v101 PowerPack which includes updates to support Python3 compatibility. Revised the SL1 12.2.5 release notes to include a note about upgrading from MariaDB 10.4 to 10.6.AMQP: RabbitMQ v103 Py3 PowerPack Release Notification
We are pleased to announce that the AMQP: RabbitMQ v103 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/aBu0z000000XZD8CAO/amqp-rabbitmq The following enhancements and addressed issues are included this release of the "AMPQ: RabbitMQ": Updated this PowerPack to be Python3 compatible. NOTE: When discovering a standalone RabbitMQ device or cluster, you must use this PowerPack in conjunction with the Cisco: Cloud Center PowerPack to properly classify the RabbitMQ device or cluster. If you do not, the RabbitMQ device or cluster will remain classified as "Pingable". Please refer to the AMQP: RabbitMQ v103 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the AMQP: RabbitMQ v103 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The AMQP: RabbitMQ v103 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the AMQP: RabbitMQ v103 Py3 PowerPack Release can be found in the Release Notes.
