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
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.
ServiceNow Incident Sync Pack & RBAs
Hi all, I am currently trying to configure some Run book automation policies to enrich data in ServiceNow incidents, sending the RBA output into the Incident worklog, and have hit a bit of a road block on the best way to configure the RBA criteria. Background: We use a dedicated "ServiceNow: [Incident] - Add/Update" RBA for each organisation, which is triggered on event creation, to effectively "Auto Ticket" on all events for specific SL orgs (excluding masked and child rollup). Challenge: In my Enrichment RBA's I want to trigger using "and external ticket IS created", to ensure that I am only posting updates when there has been a ServiceNow incident created. However the OOTB ServiceNow Incident sync pack is updating the events external ticket ref field with various messages e.g. "Sync Successful", before the event is updated with the Incident Number. As soon as the Incident Create updates the events external ticket ref field, by Automation policy gets triggered (I assume because from the RBA's point of view, it has a value in the field) to update the Worklog. Does anyone have any suggestions on the best way to ensure that an "Enrichment" RBA is only triggered only once it has a real SN incident number returned? Many thanks in advance. Neil
CMDB Sync - Attributes Sync per ci class
Hallo This is more of a PowerFlow discussion on the CMDB Sync pack. Currently the mapping of attributes is not restricting on what class have what attributes. It is mostly coming down to what we currently have it map within ScienceLogic. The fun of that is that the PF will come down to some weird attributes association with different class, even when that attributes does not exist. Example Blade and CPU counts are certainly not an attributes of wap_network Ci class, however PF will put that together and make the payload a bit bigger and send over to ServiceNow. Then it gets ignored. While that we also cannot see the Ignore on the PF Debug. { "className":"cmdb_ci_wap_network", "values":{ "x_sclo_scilogic_monitored":true, "x_sclo_scilogic_id":"123456", "x_sclo_scilogic_region":"ScienceLogic", "x_sclo_scilogic_url":"https://support.sciencelogic.net/em7/index.em7?exec=device_summary&did=123456", "object_id":"BR_1_AP", "company":"a9b548781be235496287bc4bcb4bcb04", "sys_domain":"3d854c381be230502c496287bc4bcbd3", "short_description":"Description: Fortinet.AccessPoint, Device Class: Fortinet | FortiAP", "u_public_ip_address":"10.11.10.4", "u_operation_state":"connected", "serial_number":"FP432FTF000000001", "u_software_version":"FP432F-v7.4-build0540", "version":"FP432F-v7.4-build0540", "u_uuid":"f039250e-4878-51ef-42f2-f0b32e139f7d", "cpu_count":0, "cpu_speed":0, "first_discovered":"2025-01-23 19:11:03", "firmware_version":"FP432F-v7.4-build0540", "u_firmware_version":"FP432F-v7.4-build0540", "os":"FP432F-v7.4-build0540", "fqdn":"BR_1_AP", "host_name":"BR_1_AP", "u_discovered_manufacturer":"Fortinet", "manufacture":"Fortinet", "u_discovered_model_number":"432F", "model":"432F", "model number":"432F", "name":"BR_1_AP", "blade_serial_number":"FP432FTF000000001", "cost":0 },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.F5: Big IP DNS v101 Py3 PowerPack Release Notification
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.IBM Storwize (SVC) Powerpack no longer compatible
We have recently been caught off guard with this issue, we are monitoring a lot of IBM storage and as their firmware has been upgraded, we have lost the ability to monitor them. This includes Storwize v5000 and FlashSystems 5000, 7000 & 9000 series. As mentioned on the SVC powerpack page "ScienceLogic uses the SMI-S API to communicate with IBM storage and requires the storage system to use SMI specification version 1.6.0 or higher" - if you have an IBM Storwize running 8.6.0.2 or above you will no longer be able to monitor it using ScienceLogic. IBM have transitioned to using REST API. https://support.sciencelogic.com/s/release-version/aBu0z000000XZPdCAO/ibm-svcSL1 PowerFlow v3.1.0 is Released
Hello, We are pleased to announce the release of SL1 PowerFlow v3.1.0, which includes important updates and fixes to Issues that were previously reported to ScienceLogic. This release also includes the powerflowcontrol (PFCTL) Command-line Utility and the Base Steps SyncPack v1.5.6. Also available on the release download page are the SL1 PowerFlow Flow Control SyncPack v1.0.2 and the SL1 PowerFlow System Utils SyncPack v1.1.7. This release includes some important updates to the PowerFlow user interface, such as: A persistent footer now displays system information, including a last login timestamp and the PowerFlow version installed. A new green badge on scheduled applications that indicates how many schedules exist for the application, giving you at-a-glance information about your applications without your needing to open each application to see more information. The active version of a SyncPack on the SyncPacks page is now displayed separately from other installed versions. An "Export to CSV" option on the SyncPacks page that lets you export a CSV file containing the complete list of SyncPacks and all relevant information about them. To learn more about SL1 PowerFlow version 3.1.0, please see the release notes or the user manual: SL1 PowerFlow version 3.1.0 Release Notes SL1 PowerFlow version 3.1.0 Manual To learn more about updates included in powerflowcontrol (PFCTL) Command-line Utility, see the release notes: powerflowcontrol (PFCTL) Command-line Utility Release Notes Thank you, Release Management
ScienceLogic Job: VP of Engineering and Product
What we’re looking for… The ScienceLogic SL1 product has been recognized as an industry leader in the emerging space of AIOps – technologies that leverage ML-based insights to deliver increasingly autonomous, self-healing IT services. We’re looking for a world-class product leader to take the reins of the flagship SL1 product – and evolve it to meet the needs of current and future enterprise customers for the next decade. Successful candidates will possess exemplary technical depth, IT domain expertise, and a passion for product and engineering excellence - as well as a proven track record for delivering modern, cloud-based enterprise services. The VP Product will report to the CPO and have primary responsibility for guiding the strategy and delivery of SL1. What you'll be doing... Define the strategic direction for ScienceLogic SL1 – core platform as well as UI/UX – including technologies around collection/ingestion, transport, data model and storage, programming interface, and runtime architecture (container-based microservices). Lead and grow a team of high-performance engineers and product managers. Ensure efficiency and predictability of execution through clear accountability, goals, standards, and metrics. Develop strong partnerships with global sales, marketing, and engineering teams to create products that deliver on the company’s revenue, margin and broader business objectives. Reinforce a culture composed of accountability, customer-focus, and passion for excellence. Work with the CPO, executive/senior leadership team, and other stakeholders to ensure alignment of high value projects to revenue generation and business objectives. Manage capacity, capability, and availability to ensure resource allocation meets aggressive growth business commitments. Communicate plans and roadmaps to all constituents on a timely basis. Mentor and coach the product teams on developing a culture of product innovation. Visit the Job Posting for more details about the role and to applyScienceLogic Job: Senior Software Test Engineering Lead
What we’re looking for… ScienceLogic is looking for a QA lead who will be responsible for leading all testing efforts to ensure the highest quality and performance standards for the Skylar product. This role requires hands-on technical expertise, strategic planning abilities, software development skills and a strong collaborative approach. Working closely with development teams, product management, and other QA resources, you will develop and execute a robust testing strategy, ensuring that Skylar meets all quality, functionality, and performance requirements. What you’ll be doing… Develop, implement, and manage a comprehensive QA strategy for the Skylar product, ensuring alignment with project timelines and goals. Lead a team of QA engineers and testers, both onshore and offshore, in executing functional, performance, integration, and regression testing. Collaborate with cross-functional teams (developers, product managers, UX designers) to understand requirements, define testing scope, and maintain quality standards. Design and execute test plans and cases, covering all aspects of the product, including functional, usability, performance, and security testing. Identify, document, and track issues through resolution using industry-standard defect tracking tools. Establish test metrics, KPIs, and quality benchmarks, regularly reporting on quality status, trends, and risk to stakeholders. Act as the subject matter expert on QA processes, providing guidance on best practices and industry standards. Drive automation initiatives and strategies, ensuring a balance between automated and manual testing where appropriate. Ensure testing practices align with ScienceLogic's compliance, security, and data protection standards. Visit the Job Posting for more details about the role and to apply
