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
How to test SL1 backups
In any decent enterprise there is a requirement to backup system and also do periodic tests for restoring data from backups. Is anyone here doing some kind of testing for those backups that SL1 makes. Testing directly to production stack is pretty heavy and disturbing effort, especially if there are some issues in backup. So do you have special routines to test those backups?What Topics are you interested in seeing at the Nexus Live Conference?
The Nexus Live conference is right around the corner October 7-9, 2025 Reston, VA. We have all kinds of great topics on the agenda including Goal-Driven Automation Intelligent Observability Service-Centric Operations Some of our presentations, demos and workshops are still in development. We want to make sure and provide content that you find interesting and useful. What are some topics that you would like to learn more about or see demos on? Share your ideas in the comments for some free ScienceLogic Swag and the opportunity to help shape the conference. Oh- and I will have a booth there to go through Nexus Community training, topics and gather your feedback. Cheers- Sara LeslieRegister Now for the Nexus Live Conference October 7-9, 2025 | Reston, VA
1 MIN READ Your Peers. Your Community. Your Event. Nexus Live 2025 is an immersive learning experience, and a one-of-a-kind connection that brings the ScienceLogic community together for three days to share knowledge, network, and meet industry thought leaders. At Nexus Live (formerly Symposium), you can ideate how to empower IT to solve your most challenging concerns. From Proactive Observability and AI-Driven Operations solutions to Intelligent Automations, our conversations will be meaningful and relevant to you! The age of the IT champion has arrived—and their greatest ally is agentic AI. Be a part of the Nexus Live magic. Register NowCisco: Intersight v102 PowerPack Release Notification
We are pleased to announce that the Cisco: Intersight v102 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/aBu4z000000R0BGCA0/cisco-intersight Features The following enhancements and addressed issues are included in this release: Updated the PowerPack to support the OpenAPI schema version 3 (ECDSA) in the credential. Removed the "Cisco: Intersight Alarms Configuration" Dynamic Application and replaced it with the "Cisco: Intersight Alarms Performance" Dynamic Application for enhanced functionality. The snippet code and collection objects of the following Dynamic Applications were updated to support Intersight pagination, to filter the default organization, and to prevent components from switching between organizations. For more information, see Monitoring Cisco: Intersight: Cisco: Intersight Blade Server Discovery Cisco: Intersight Chassis Discovery Cisco: Intersight Fabric Interconnect Discovery Cisco: Intersight Organization Discovery Cisco: Intersight Rack Units Discovery Cisco: Intersight Alarms Performance Updated collection object requests to retrieve only the required information in the "Cisco: Intersight Blade Server Configuration" Dynamic Application. Please refer to the Cisco: Intersight v102 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: Intersight v102 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: Intersight v102 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: Intersight v102 PowerPack Release can be found in the Release NotesRestorepoint 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 Management
Dynamic device group automation with GQL
I have a script that manages devices groups. The groups are simple, using a single rule, custom attribute SiteID = xxxx. Because the legacy API does not allow for the creation/application of the rules, I was directly manipulating the DB. We are moving to SAS - no more direct DB access. I need some GQL magic to create/apply a rule to a group.
ScienceLogic rest api x-em7-run-as header validation
We discovered that after updating our SL1 platform from 12.1 to 12.3 that the validation of the rest api request header "X-EM7-RUN-AS" has changed and is now more strict. In SL 12.1, we can (for example) delete an event using admin credentials and use the x-em7-run-as header to actually execute the request on behalf of a different user (in our scenario we use a customer-specific account). We used '/api/account/<accountid>' as a value for this header. Since SL 12.3 (or somewhere after 12.1), we noticed that '/api/account/<accountid>' is no longer accepted: any rest api call using the x-em7-run-as with value '/api/account/<accountid>' will return a HTTP 401 Unauthorized with corresponding message: { "errors": [ { "errorcode": "NO_AUTH", "message": "Valid authentication credentials not provided" } ], "messages": [], "resource_body": null } However, if I simply put '<accountid>' as the value for this header, the request succeeds. Can you please improve the documentation (https://docs.sciencelogic.com/api-developer-docs/Content/Web_Content_Dev_and_Integration/ScienceLogic_API/methods_headers_and_responses.htm#request-headers) and specify that the value for this header must be a number which matches a real user in the system. Also, the request also fails when using an account id value and that account is Inactive. Would be nice to read it in the docs. error message when trying to execute an action on a suspended user: { "errors": [ { "errorcode": "NO_AUTH", "message": "Account \u0027em7admin\u0027 failed authentication due to 1 account restriction(s)" } ], "messages": [ "This account is marked as \u0022inactive\u0022" ], "resource_body": null }Cisco: Meraki API v115 Py3 PowerPack Release Notification
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 Notes
