ScienceLogic's PowerFlow Training: Explore Built-In Integration and Custom Automation Capabilities
PowerFlow is ScienceLogic’s integration platform designed to seamlessly extract, transform, and load data between SL1 and third-party tools. Whether you're implementing built-in integrations or creating custom automations, PowerFlow empowers you to streamline workflows, integrate systems, and enhance IT operations. Find the Right Training for Your Needs Explore training options based on your role and objectives: PowerFlow: ScienceLogic's Bi-Directional Task Execution Platform (1 hour) Discover PowerFlow’s core functionality in this introductory learning path, covering key features, configuration, navigation, and troubleshooting. PowerFlow Integrations: ServiceNow (4 hours) Master PowerFlow’s integration with ServiceNow. This comprehensive learning path includes all content from the introductory PowerFlow course, then dives deeper into implementing SL1 and ServiceNow integration use cases. PowerFlow: Software Development Kit (SDK) (1 hour) For advanced users, this training course shows how to use the PowerFlow Software Development Kit (SDK) to build custom SyncPacks for automation, system integration, and workflow enhancements. Access Training Anytime, Anywhere ScienceLogic University is ScienceLogic's on-demand learning portal. Log in or create an account here to access these PowerFlow training options and other essential topics.30Views0likes0CommentsOptimising PowerFlow Integrations: Isolating Incident and CMDB Workloads
In complex IT environments, integrations like incident management and Configuration Management Database (CMDB) synchronisation are pivotal. ScienceLogic's PowerFlow platform offers robust capabilities to handle these integrations. However, to ensure optimal performance and prevent resource contention, it's crucial to configure dedicated steprunners and queues for different workloads. This article discusses on-premises instances of PowerFlow. If you are using a SaaS-hosted instance of PowerFlow, please submit a service request via the Support Portal outlining your requirements. The relevant team will then review your request and discuss the necessary changes to be made on your SaaS instance of PowerFlow. Understanding the Challenge Incident management and CMDB synchronisation have distinct characteristics: Incident Management: Typically involves lightweight, high-frequency tasks that require rapid processing to maintain real-time responsiveness. CMDB Synchronisation: Often deals with bulk data operations, such as syncing large volumes of configuration items, which are resource-intensive and time-consuming. Running both integrations on the same steprunner can lead to performance issues. For instance, a heavy CMDB sync might consume significant resources, delaying the processing of critical incident tasks. Implementing Dedicated Steprunners and Queues To address this, PowerFlow allows the configuration of steprunners to listen to specific queues. By assigning separate queues for incident and CMDB tasks, you can isolate their processing and allocate resources appropriately. Example Configuration Here's how you might define dedicated steprunners in your docker-compose.override.yml: Incident Steprunner: steprunner-incident: image: sciencelogic/is-worker:latest hostname: "incident-{{.Task.ID}}" deploy: resources: limits: memory: 2G replicas: 10 environment: user_queues: 'incident_queue' worker_threads: 4 CMDB Steprunner: steprunner-cmdb: image: sciencelogic/is-worker:latest hostname: "cmdb-{{.Task.ID}}" deploy: resources: limits: memory: 4G replicas: 5 environment: user_queues: 'cmdb_queue' worker_threads: 2 In this setup: user_queues: Assigns each steprunner to a specific queue (incident_queue or cmdb_queue), ensuring isolation of workloads. worker_threads: Defines how many concurrent tasks each steprunner container can process. Higher for incidents because incident syncs are typically lightweight and frequent. Lower for CMDB to reduce memory contention since CMDB data is often bulkier and more complex. deploy.resources.limits.memory: Caps how much memory each steprunner container can use. This helps prevent individual steprunners from consuming excessive memory, which is especially important when running many containers on shared infrastructure. Example: 2G for incidents (moderate), 4G for CMDB (higher due to heavier payloads). deploy.replicas: Specifies how many containers to run for each steprunner service. More replicas for incidents to handle high throughput. Fewer for CMDB, since each task may take longer and use more resources. Benefits of Isolation Performance Optimisation: Ensures that resource-heavy CMDB tasks don't impede the processing of time-sensitive incident tasks. Scalability: Allows independent scaling of steprunners based on the workload demands of each integration. Resource Management: Facilitates fine-tuned allocation of system resources, reducing the risk of bottlenecks and failures. Monitoring and Adjustments Regular monitoring is essential to maintain optimal performance: Queue Lengths: Persistent growth in queue lengths may indicate the need for additional steprunners or increased thread counts. Resource Utilisation: Monitor CPU and memory usage to prevent over utilisation. Error Rates: High error rates might necessitate adjustments in configurations or error-handling mechanisms. Final Thoughts By strategically configuring dedicated steprunners and queues for incident and CMDB integrations, you can enhance the efficiency, reliability, and scalability of your PowerFlow environment. This approach ensures that each integration operates within its optimal parameters, delivering better performance and resource utilisation.72Views4likes0CommentsConnect with a PowerFlow Product Manager
We Want Your Insights! We would love to connect with you one-on-one to gather your feedback and insights about PowerFlow. Your experiences are key to shaping the future of our product! Why Chat? Share your thoughts on how we can improve Discuss any challenges you’ve faced Help us prioritize features that matter to you Please note that these calls are not intended to address issues that can be resolved through Support Cases. Ready to make an impact? Book a call with us now! Thanks for being part of our journey!39Views1like0CommentsConvert Customization to PowerFlow Jinja Template
Sometimes when syncing devices from SL1 into ServiceNow as a Configuration Items there can be a mismatch. ServiceNow may list the name as Fully Qualified Domain Name and SL1 will use short name. This setting can be updated in SL1, but in some cases the SL1 team would rather see short name than FQDN. This can be setup on a per SL1 Device Class basis. PowerFlow Using the following Jinja2 “if statement” the device name in SL1 can be converted to use “Device Hostname,” in SL1 instead for Microsoft SQL Server Databases. This excerpt of code would go under attribute mappings for name on the ScienceLogic side mapping to name on the ServiceNow side: {%- set output = [] -%} {%- if (device.device_class|trim) in ['Microsoft | SQL Server Database'] } {%- set output = device.hostname -%} {%- else -%} {%- set output = device.name -%} {%- endif -%} {{ output }} Example:26Views0likes0CommentsPowerFlow 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 Management17Views1like0CommentsServiceNow Base SyncPack v3.8.2
Hello, We are pleased to announce the release of the ServiceNow Base version 3.8.2 SyncPack. The following feature was addressed in this release: Added updates to support "ServiceNow CMDB" SyncPack version 3.6.2. This release is made to work with SL1 version 12.1 or later SL1 PowerFlow version 2.6.0 or later Base Steps SyncPack version 1.5.5 or later ServiceNow version Tokyo or later, with Web Services enabled With the release of this SyncPack, older versions of the ServiceNow Base SyncPack have been suspended. Thank you, Release Management22Views0likes0CommentsServiceNow CMDB v3.6.2 SyncPack
Hello, We are pleased to announce the release of the ServiceNow CMDB v3.6.2 SyncPack. The following enhancements and issues were addressed in this release: Addressed an issue that caused incorrect relationships to be sent to ServiceNow when only child devices were sent for updates. (Case: 00492036) Addressed an issue with the "Sync Devices with SQL" application that caused the device collection mode/state to always show as "active" when synced to ServiceNow, regardless of the actual device state. (Case: 00489043) Addressed an issue where CI classes in ServiceNow with a 'region' field caused issues with disconnects being sent from PowerFlow. The 'region' field from ServiceNow on a CI is now saved on the Python object as "snow_ci_region". (Case: 00493761) Updated the SyncPack to correctly handle an SL1 platform change starting in version 12.1.0 for creating custom links through GraphQL. This release is made to work with SL1 version 12.1 or later SL1 PowerFlow version 2.6.0 or later Base Steps SyncPack version 1.5.5 or later ServiceNow Base SyncPack version 3.8.2 or later ServiceNow version Tokyo or later, with Web Services enabled ScienceLogic SL1: CMDB & Incident Automation certified application version 1.0.81 With the release of this SyncPack, older versions of the ServiceNow CMDB SyncPack have been suspended. Thank you, Release Management24Views0likes0CommentsScienceLogic - ServiceNow Integrations: ITOM Licensing Requirements
ScienceLogic maximizes customers' investments in ServiceNow through its powerful suite of pre-built integrations, referred to as SyncPacks. ScienceLogic offers certified ServiceNow scoped applications for streamlined platform integration, accessible via the ServiceNow Store, ensuring seamless compatibility. Understanding the licensing requirements for ServiceNow integrations is crucial for informed decision-making. This document seeks to clarify the IT Operations Management (ITOM) licensing requirements for ScienceLogic integrations with ServiceNow. Its purpose is to eliminate any confusion regarding which integrations necessitate ITOM licensing. Note: ServiceNow’s ITOM licensing is further organized into different tiers. This document is not intended to help identify the suitable tier for your requirements. For any questions related to this, please contact ServiceNow. Scoped Application ServiceNow Module ITOM License requirement ScienceLogic SL1: Customer Service Management Integration Customer Service Management - Cases No ScienceLogic SL1: Incident Automation IT Service Management - Incident No ScienceLogic ServiceNow Integration IT Service Management - CMDB * Situational ScienceLogic SL1: Service Catalog Automation IT Service Management - Service Catalog ** Situational Service Graph Connector for ScienceLogic IT Operations Management - CMDB Yes ScienceLogic Event Integration IT Operations Management - Events Yes * ScienceLogic is actively adding support for cloud infrastructure mappings within our integrations. To effectively leverage these features in accordance with ServiceNow best practices, you might require ITOM licensing. Customers can contact their ScienceLogic representatives for cloud mapping questions. ** ITOM licenses are necessary only if you are implementing a CMDB using ITOM FAQs Here are some frequently asked questions (FAQs) from our customers Q: Are there other scenarios where one would need IT Operations Management (ITOM) licenses for CMDB? A: The necessity for ITOM licenses is primarily influenced by the specific goals of your organization. Customers of ScienceLogic are not required to adopt ITOM unless their integration module is inherently ITOM-based. We observe that customers generally opt for ITOM in the following situations: To deploy out-of-the-box ServiceNow automation for ensuring data quality and reliability. When transitioning to a more advanced, ServiceNow-defined CSDM (Common Service Data Model) framework. Q: Do Business Services in ScienceLogic need IT Operations Management (ITOM) licenses to be integrated into ServiceNow? A: No, it does not. ScienceLogic integrations leverage out-of-the-box ServiceNow CMDB tables, eliminating the need for ITOM licenses. You can effectively replicate ScienceLogic Business Service Models in ServiceNow by leveraging our integrations. Customer Testimonials Discover what our customers are saying about our integrations. “ We like that ScienceLogic has a tight integration with ServiceNow and particularly the fact that we don't need to deploy the additional discovery modules from an integration perspective. ” “ We are able to have a single pane of glass using ServiceNow. All monitoring events and CMDB population is managed by ServiceNow. ScienceLogic is a great monitoring system that integrates well with ServiceNow using its integration server, which provides workflow and rules that work with our systems. ”48Views1like0CommentsPowerflow Application Queue Trigger Failure
Hi All, I've Developed a Runbook Action within ScienceLogic, that triggers a Powerflow Application if certain Runbook Automation Policy conditions are met. Upon execution, it sends the following payload: "params": { "configuration": configuration, "event_policy_name": EM7_VALUES['%_event_policy_name'], "event_details": EM7_VALUES, "organization_name": EM7_VALUES['%O'], "system_url": system_url, "queue": queue } These parameters are specified as inputs, and some are derived from the EM7Values. When the Runbook Automation linked to this Action executes against a specific Event Policy raised on a Device, i can see a success message in the "Event Notifications" window, and i can see all inputs and variables are passed through in its entirety. The real issue comes when you open Powerflow. The Application immediately fails, and an error message stating that theres an "Internal Request Error: pop from empty list". This error doesnt make any logical sense as the parameters i pass through are either JSON or String Payloads, no Arrays. I've been doing testing with the payloads, ensuring that the configuration being referenced exists, and confirmed all these are in place and are working fine. I then removed the "queue" value from the params body, and only passed the rest of the parameters, this succeeds and the application executes without incident. What's interesting, even if manually executing the application in the UI with a custom parameter set, as soon as you specify the queue, it fails. Now its important to know that we've only recently created the queues on a development system, and this is the first time we're testing with the newly created queues. I was hoping that someone in this community might be able to shed some light as to why this might be happening? Could it be that the queues are unreachable, and therefor when not specifying the custom queue, it defaults to the celery queue, which are reachable, and therefor works? If the queues are the problem, what could be done to try and fix the problem? Any and all contributions are welcome. Sincerely Andre26Views0likes0Comments