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
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 Management
This week's updates to the Doc sites at docs.sciencelogic.com
3/21/25 Doc updates to the main docs site at https://docs.sciencelogic.com/ Updated the section on SL1 Self-Monitoring with revised instructions for creating and aligning credentials for monitoring SL1 devices. Added a sample credential to the Cisco: AppDynamics v105 PowerPack that includes CURL options for SSL verification, added a new threshold for the "Cisco: AppDynamics Application Discovery" Dynamic Application, and updated the the "Cisco: AppDynamics Application Discovery" run book action. Added the PowerFlow v3.1.1 manual. 3/21/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Added a sample credential to the Cisco: AppDynamics v105 PowerPack that includes CURL options for SSL verification, added a new threshold for the "Cisco: AppDynamics Application Discovery" Dynamic Application, and updated the the "Cisco: AppDynamics Application Discovery" run book action. Added the PowerFlow 3.1.1 release notes Added the PowerFlow powerflowcontrol (pfctl) Command-Line Utility 2.7.11 release notes
How to Configure SSO Support for Global Manager
4 MIN READ Enabling SAML-Based SSO in ScienceLogic Global Manager ScienceLogic Global Manager (GM) is a powerful appliance designed to aggregate and display data from multiple SL1 systems, providing a centralized view of your entire infrastructure. Starting with SL1 version 12.2.1, ScienceLogic introduced support for Security Assertion Markup-Language (SAML) based Single Sign-On (SSO), simplifying authentication and enhancing security. This guide, walks through the process of enabling SAML-based SSO in ScienceLogic Global Manager, so that user access can be managed seamlessly and improve operational efficiency. Why Enable SAML-Based SSO? Enabling SSO through SAML allows users to log in once and gain access to multiple SL1 systems through the Global Manager providing the users are already authorized to access the target systems. This streamlines Identity and Access Management (IAM), reduces password fatigue, and strengthens the organization's security posture. Getting Started: Before beginning, ensure the following is true: SL1 Version: 12.2.1 or later Access Level: Administrator access to the Global Manager appliance. Prerequisites: ScienceLogic assumes that the "SL1: Global Manager" PowerPack has been installed and the child stacks have been discovered. No platform version mismatch between the GM and the child SL1 Stacks AP2 version across all Stacks as a minimum must be Gelato v8.14.26 The Child SL1 stacks are configured to authenticate using SSO authentication A local administrator account must exist on each Child Stack that GM can use to authenticate with the child stack. GM SSO authentication resource must be configured to authenticate with the same Identity Provider (IdP) configured on the Child SL1 stacks The ‘/opt/em7/nextui/nextui.conf’ file on the GM must have the following variable configured - If the GM platform is hosted by ScienceLogic a Service Request must be raised using the ScienceLogic Support Portal here to request an addition of the environmental variable: GM_STACKS_CREDENTIAL=enabled GM_STACKS_CACHE_TTL_MS=0 GM_SESSION_AUTH_CACHE_TTL_MS=0 GLOBAL_MANAGER_SESSION_COOKIE_CACHE_TTL_MILLIS=0 Unique SL1 Administrator accounts must exist on each child stack – These act as a global API key for users which allows authentication on the child stack. Once a user authenticated, the user data is loaded on to GM and the request proceeds as normal. Step 1: Configure Basic/Snippet Credentials a) Access GM UI and logon using an Administrator Account b) Navigate to Credentials page (Manage > Credentials) and Select ‘Create New’ followed by ‘Create Basic/Snippet Credential’. A dialog window will be presented, this must be completed with the details listed in the table below for each child stack using the Administrator Credentials to enable GM to authenticate with the child stacks Fields Values Name stack-<stack-id>-gm-auth All Organizations Toggled Timeout (ms) 0 Username <Target-Child-Stack-Admin-Username> Password Unique Password Hostname/IP <Target-Child-Stack-IP> Port. 443 c) Perform Credential Test using the Credential Tester and confirm the authentication is successful. Step 2: Credential Alignment - GraphQL Following the creation of the Basic Credential, each child stack credential must be aligned using GraphQL (GQL) mutation – The command requires supplying the ‘guid’ of the credentials created above in step 2 above. The following GQL will return all credentials created in Step 1 above providing the credential names contain ‘GM’. Access the GQL Browser by appending /gql to the GM URL I.E. https://<GlobalManager_HOST>/gql - This will provide access to the GQL Browser. Query: query allCreds{ credentials (search:{name:{contains:"GM"}}) { edges { node { id guid name definition } } } } Example Response: The example response shows the required ‘guid’ - Ensure a note of each ‘guid’ associated with each credential is noted for Step 4. { "data": { "credentials": { "edges": [ { "node": { "id": "41", "guid": "3C07AB8B0655A722712C46FA1DF821EA", "name": "stack_1_gm_auth", "definition": [..] } } ] } } } Step 3: Retrieve GM Stack ID The following GQL will return all existing Child SL1 Stacks present on the GM. Query: query getallstacks { globalManagerStacks { edges { node { id name credential { guid name } } } } } Example Response: Note the ‘id’ representing the GM Stack-ID’s for the next step. { "data": { "globalManagerStacks": { "edges": [ [..] { "node": { "id": "3", "name": "<sl1_stack_hostname>", "credential": null } } [..] } Step 4: GraphQL Credential Mutation The following GQL mutation will align the Basic Credential to permit GM to authenticate with the target child stacks. Mutation: mutation aligncred { alignGlobalManagerCredential(id: <Stack-ID>, credential: "<guid>") { id name credential { id name guid } } } Replace: with the GM Stack-ID for each child stack retrieved from Step 3. with the credential GUID from Step 2 that is associated with the same Child Stack. Example Mutation Response: { "data": { "alignGlobalManagerCredential": { "id": "3", "name": "<child_stack_name>", "credential": { "id": "41", "name": "stack_1_gm_auth", "guid": "3C07AB8B0655A722712C46FA1DF821EA" } } } } Repeat the above mutation for the remaining Child SL1 stacks discovered on GM. Summary Enabling SAML-based SSO in ScienceLogic Global Manager streamlines authentication, enhances security, and improves operational efficiency by allowing users to seamlessly access multiple SL1 stacks with a single login. By following the outlined steps — configuring credentials, aligning them via GraphQL, and ensuring proper authentication setup —organizations can integrate SSO effectively while maintaining secure access controls. After completing these steps, users will be able to log in once and have visibility of managed devices across multiple SL1 stacks via GM, enhancing productivity and reducing security risks. By leveraging SAML-based SSO, ScienceLogic not only simplifies access but also strengthens the overall security posture. If there are issues encountered, please contact ScienceLogic Support here. For further details related to GM setup, refer to the official ScienceLogic documentation here.Cisco: Viptela v200 Py3 PowerPack Release Notification
We are pleased to announce that the Cisco: Viptela 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/aBu0z000000XZMACA4/cisco-viptela Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Added the new "Cisco: Viptela Environment v200" Execution Environment to support conversion to the Snippet Framework. Converted the PowerPack and all Dynamic Applications to support Python 3 using the Snippet Framework. Added the new "Cisco SDWAN/Viptela" universal credential type and guided discovery workflow. Made a number of updates to the "Cisco: Viptela Events" Dynamic Application: Consolidated functionality from the "Cisco: Viptela Events Caching" Dynamic Application into this Dynamic Application. Added the new "API Alarms" collection object to trigger the API request. Changed page size to 40 to reduce the number of requests made to the API. Added a query parameter to reduce the number of alarms retrieved from the API to only those from the last hour. This can be customized in the snippet by adjusting the polling frequency. NOTE: Upon upgrading from a version of this PowerPack using Python 2, duplicate alerts may be created due to incompatibility of the cached values from Python 2 to Python 3. Deprecated the following Dynamic Applications: Cisco: Viptela Token Configuration Cisco: Viptela Events Caching Added proxy support to the PowerPack. NOTE: The HTTPS proxy scheme is only available using the new universal credential. Existing SOAP/XML credentials do not support switching the scheme. Please refer to the Cisco: Viptela v200 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: Viptela v200 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: Viptela v200 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: Viptela v200 Py3 PowerPack Release can be found in the Release NotesCan't get new device icon to show
Hi all, I'm trying to upload a new device icon for a custom Powerpack I'm creating (Ruckus SNMP). I've taken a screenshot of the logo as a .png. First I tried to follow the documentation here, found a tool to convert the png to a svg, and SL shows me an error: Next, I just tried uploading the png in various sizes (128, 300, and 600). All of them successfully upload, and show an actual icon the Icon browser minus that grey frame (see screenshot below). However, when I apply this Icon in the Device Class view, the device itself just shows a blank window where the icon would be. Anyone had any experience doing this?PowerFlow v3.1.1 & PFCTL 2.7.11 Release
Hello, We are pleased to announce the release of PowerFlow v3.1.1 and PFCTL v2.7.11, which contain important fixes to the PowerFlow 3.1.0 and PFCTL v2.7.10 releases. Please read the Release Notes carefully before installing these releases. These are the highlights only. FEATURES This section covers the features that are included in SL1 PowerFlow Platform version 3.1.1: The following images are included in this release of PowerFlow: registry.scilo.tools/sciencelogic/pf-api:rhel3.1.1 registry.scilo.tools/sciencelogic/pf-couchbase:6.6.0-13 registry.scilo.tools/sciencelogic/pf-dex:2.37.1-10 registry.scilo.tools/sciencelogic/pf-worker:rhel3.1.1 registry.scilo.tools/sciencelogic/pf-gui:3.1.1 registry.scilo.tools/sciencelogic/pf-pypi:6.3.1-14 registry.scilo.tools/sciencelogic/pf-rabbit:3.8.35-6 registry.scilo.tools/sciencelogic/pf-redis:6.2.14-5 ISSUES ADDRESSED The following issues were addressed in this release: Addressed an issue that prevented new schedules from functioning correctly if an application used an ID with both upper and lowercase letters. (Case: 00495740) Jinja2 is now available in the PowerFlow Devpi Server, which allows the ServiceNow CMDB SyncPack to use it while rendering templates. (Case: 00492419) Thank you, Release ManagementCisco: AppDynamics v105 PowerPack Release Notification
We are pleased to announce that the Cisco: AppDynamics v105 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/aBu0z000000XZJuCAO/cisco-appdynamics Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Added the "AppDynamics Example - SSL" credential that includes CURL options enabled for SSL verification. Added the "Search Applications on all Organizations" threshold to the "Cisco: AppDynamics Application Discovery" Dynamic Application. Updated the "Cisco: AppDynamics Application Discovery" run book action to ignore the organization name when creating, renaming, and deleting applications. You can enable or disable it using the "Search Applications on all Organizations" threshold in the "Cisco: AppDynamics Application Discovery" Dynamic Application. The threshold is enabled by default. NOTE: ScienceLogic recommends you keep the threshold enabled only if you want to monitor AppDynamics applications across multiple organizations. Otherwise, disable the threshold if you want to monitor AppDynamics applications in the default organization that has the controller. Added the following Dynamic Applications: Cisco: AppDynamics Business Transaction Configuration Cisco: AppDynamics Business Transaction Discovery Cisco: AppDynamics Backend Configuration NOTE: ScienceLogic recommends manually aligning the Dynamic Application to the AppDynamics Application device after upgrading the PowerPack to version 105. Updated the "Cisco: AppDynamics Application Template" Dynamic Application to include the "Cisco: AppDynamics Backend Configuration" Dynamic Application. Please refer to the Cisco: AppDynamics v105 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: AppDynamics v105 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: AppDynamics v105 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: AppDynamics v105 PowerPack Release can be found in the Release Notes
GQL Device linked to Collector
Hi, For trouble shoot, I want to have an overview of the devices linked to the collector where the (SNMP) device is allocated to. Pulling all the devices with attributes are working fine, also the related collector group and his group members. I am not able to find a solution to get device-to-collector. Is someone having a example GQL? Any suggestions? Thanks in advance. AlfredEvent Policies and More - Event Management in ScienceLogic SL1
In this video, we explore event policies in ScienceLogic's SL1 platform including how to edit, customize, and create them. You'll learn about event sources, match criteria, and how to manage events using regular expressions, auto-expiration, and suppression. The video also covers the use of power packs for event categorization and monitoring, as well as role-based access control. Learn more about event management in SL1: https://sciencelogic.com Or visit our Support Center for more videos and customer resources.
Event Notification and Automation - Event Management in ScienceLogic SL1
In this video, we demonstrate how to respond to events using power packs. You'll learn how to take actions on events, view vital information, run diagnostic tools, and integrate with your service desk. The video also covers role-based access control and automated actions. Learn more about event management in SL1: https://sciencelogic.com Or visit our Support Center for more videos and customer resources.
Event Correlation and Masked Events - Event Management in ScienceLogic SL1
In this video, we focus on the masked events column. You'll learn how Science Logic correlates events to highlight the most important ones, masking less critical events to identify the root cause. Learn more about event management in SL1: https://sciencelogic.com Or visit our Support Center for more videos and customer resources.
