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
Please anyone can help with DB2 HADR credentials - how to ?
Please as there is no documentation does anyone successfully use DB2 HADR powerpack ? For interconnection, do I need ssh + db2 credentials combination ? Should I define some DB2 credential and then mapped to SSH credential within new Soap credential ? how to map ? Or do I need only Soap with mapped ssh id header ? Thank you very much.
How to select specific series in a dashboard graph for AIX Network Stats
We are showing the "Output Packets" metric from the "AIX: Network Stats" DA in a dashboard but we want to only show the network interface named "en1" (and not en0 etc), is this possible in a dashboard widget ? From the Device page if you look at this metric you can tick/select which interface you want to see or select the interface via "Options -> Series Selection" and we want to do the same from the Dashboard widget. Any advice really appreciated as I am struggling to find how to do this, it works ok from a Linux DA using context driven dashboard as the metrics are stored under "Interfaces" rather than "Devices" but for AIX this is not the case.
SQL Server discovery issue
I'm trying to get a SQL Server instance discovered by SL1 which refuses to even determine SQL Server is installed. All the discovery does is return this message: SQL Server discovery returned empty from SqlAppCollectionInstance data collector The Windows device seems to have no issues. SQLPS is installed and working. SQL Server permissions have been granted as required (but it doesn't appear to be getting as far as logging in to the instance - it simply doesn't recognize SQL Server is installed). I've tried rerunning winrm_configuration_wizard_v3.4.ps1, which worked for another machine that was returning the same sort of error. I've tried removing the SQL DAs and realigning via pre-defined template & credentials (which work perfectly fine for other servers in the domain). I'd rather not have to delete the Windows device and perform complete discovery from scratch; this shouldn't be necessary. Ideas? Full log from discovery session: 1. Collector Task session registered... 2. Collector is working... 3. Collector is working... 4. Collector is working... 5. Collector is working... 6. Collector is working... 7. Collector is working... 8. Process Started on Collector 9. Collecting for App ID: 1270 from Device ID: 192379 on Collector ID: 359 10. Python version 3.6.8 (default, May 24 2024, 06:39:46) 11. [GCC 8.5.0 20210514 (Red Hat 8.5.0-21.0.1)] 12. Assigned collector: 359; Root collector: None; This collector: 359 13. Collector affinity: [4] Root device collector affinity mode specified, device does not have a DCM root device. Using assigned collector. 14. Skipping scheduling of non-collectable Discovery and Label (Config Group) objects: [12550, 12551] 15. Object 12549 is enabled for collection 16. Object 12552 is enabled for collection 17. Using credential: 1216 18. Created an app object: AID: 1270 [SNIPPET CONFIG] / DID: 192379 19. Created a device object: 192379 20. Will use 10.155.210.18 as IP for device 21. Precollect for app returned True 22. Oids to collect: 23. GROUP: 1 obj_id: 12549 OID: name NAME: Name 24. GROUP: 1 obj_id: 12552 OID: unique_id NAME: ID 25. Starting collect 26. Running Snippet 1458 27. /opt/em7/lib/python3/requests/__init__.py:104: RequestsDependencyWarning: urllib3 (1.26.6) or chardet (5.0.0)/charset_normalizer (2.0.4) doesn't match a supported version! 28. RequestsDependencyWarning) 29. Reading config as a prod env 30. Reading config as a prod env 31. powershell_pywinrm_transport.connect: service: HTTP, target device: 10.155.210.18 32. callPywinrmFunction: processing output and error for Python 3 33. SqlAppCollectionInstance:_collect_data: No SQL Server instances found (standalone or clustered) 34. Snippet 1458 ran successfully 35. collected objects: {1: {12549: {'object_type': 'DynamicAppObject', 'enum': '', 'error_msg': '', 'factor': '', 'monitor_config': 0, 'name': 'Name', 'oid': 'name', 'oid_time': '0', 'oid_type': 1458, 'class': 10, 'prime': 0, 'result': [], 'std_enable': 0, 'std_min': 0, 'string_type': 0, 'trend_col': '', 'wm_walk_length': '', 'formula': ''}, 12552: {'object_type': 'DynamicAppObject', 'enum': '', 'error_msg': '', 'factor': '', 'monitor_config': 0, 'name': 'ID', 'oid': 'unique_id', 'oid_time': '0', 'oid_type': 1458, 'class': 10, 'prime': 0, 'result': [], 'std_enable': 0, 'std_min': 0, 'string_type': 0, 'trend_col': '', 'wm_walk_length': '', 'formula': ''}}} 36. AID: 1270 [SNIPPET CONFIG] / DID: 192379 thinks it was collected properly 37. AID: 1270 [SNIPPET CONFIG] / DID: 192379 had 0 bad oids (out of 1): [] 38. ================================================================================ 39. Ingestion Metadata 40. ================================================================================ 41. Collected: True 42. Collection time: 2.165022611618042 seconds 43. Found Collection Objects: [] 44. Number of Bad OIDS: [] 45. Error Message: N/A 46. Internal Alert 518: did: 192379, message: "[App ID 1270]: SQL Server discovery returned empty from SqlAppCollectionInstance data collector." 47. ================================================================================ 48. Raw Ingested Data: 49. ================================================================================ 50. Group RawIndex ObjID ObjName RawValue ElapsedTime(ms) 51. ------- ---------- ------- --------- ------------- ----------------- 52. 1 N/A 12552 ID -- NO DATA -- N/A 53. 1 N/A 12549 Name -- NO DATA -- N/A 54. ================================================================================ 55. Configuration Data for Storage: 56. ================================================================================ 57. Group Index ObjID ObjName Value PrevValue Added Changed Removed 58. ------- ------- ------- --------- ------------- --------------- ------- --------- --------- 59. 1 N/A 12552 ID -- NO DATA -- -- UNCHANGED -- 60. 1 N/A 12549 Name -- NO DATA -- -- UNCHANGED -- 61. ================================================================================ 62. Configuration Change Alerts: 63. ================================================================================ 64. -- NO CHANGE ALERTS -- 65. ================================================================================ 66. Processing app alerts... 67. ================================================================================ 68. Triggered alerts: 69. 0 triggered 70. ================================================================================ 71. DCM Component Records extracted from Configuration Data: 72. ================================================================================ 73. ======================================== 74. Discovered component records: 75. ======================================== 76. device_name unique_identifier distinguished_name uuid guid previous_unique_ids organization class_identifier_1 class_identifier_2 mac_address availability 77. ------------- ------------------- -------------------- ------ ------ --------------------- -------------- -------------------- -------------------- ------------- -------------- 78. ======================================== 79. Vanished components (by unique_id): 80. ======================================== 81. --NO VANISHED DEVICES-- 82. Dynamic App Execution Complete 83. /opt/em7/lib/python3/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release. 84. from cryptography.hazmat.backends import default_backend 85. /opt/em7/lib/python3/requests/__init__.py:104: RequestsDependencyWarning: urllib3 (1.26.6) or chardet (5.0.0)/charset_normalizer (2.0.4) doesn't match a supported version! 86. RequestsDependencyWarning) 87. Process Completed on CollectorCisco: CUCM Cisco Unified Communications Manager v114 Py3 PowerPack Release Notification
We are pleased to announce that the Cisco: CUCM Cisco Unified Communications Manager v114 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/aBu0z000000XZOzCAO/cisco-cucm-cisco-unified-communications-manager Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: All Dynamic Application using snippet arguments are now compatible with Python 3. Removed the "CUCM Credential Test" credential tester from this PowerPack. The following run book actions (RBA) are now compatible with Python 3 and will continue to function even after SL1 stops supporting Python 2: Cisco: CUCM Registration Event Cisco: CUCM Root Device Update Cisco: CUCM Subscriber Merge Please refer to the Cisco: CUCM Cisco Unified Communications Manager v114 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: CUCM Cisco Unified Communications Manager v114 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: CUCM Cisco Unified Communications Manager v114 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: CUCM Cisco Unified Communications Manager v114 Py3 PowerPack Release can be found in the Release NotesDell EMC: Isilon v104 Py3 PowerPack Release Notification
We are pleased to announce that the Dell EMC: Isilon v104 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/aBu0z000000XZWUCA4/dell-emc-isilon Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: The PowerPack was updated for Python 3 compatibility. Added the "Dell EMC: Isilon Cluster Smart Quota" Dynamic Application to collect data for all quotas associated with a cluster added to the PowerPack. Please refer to the Dell EMC: Isilon v104 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Dell EMC: Isilon v104 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Dell EMC: Isilon v104 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Dell EMC: Isilon v104 Py3 PowerPack Release can be found in the Release NotesAlibaba Cloud: Aliyun cloud Powerpack is now End of Maintenance
The Alibaba Cloud: Aliyun cloud powerpack will be transitioned from “Beta” to “End of Maintenance” support status effective immediately. The PowerPack will remain available to download and use, but ScienceLogic engineering will not maintain a development roadmap for the integration. In the event of SL1, API, or other changes that may lead to this integration ceasing to function, the expectation is that ScienceLogic engineering will not provide an updated release to address such issue. ScienceLogic reserves the right to update this product in the future if desired.
How to Generate a PowerPack Version Report in SL1 to Track Updates and Changes
3 MIN READ To successfully merge your custom changes into a new PowerPack version, you’ll need to understand how to identify the differences between versions. This process involves: Comparing the original PowerPack version (used to create your custom version) to your customized version – to identify custom changes. Comparing the original PowerPack version to the new ScienceLogic-released version – to identify new features and updates. After understanding these deltas, you can determine whether: The new version already includes features that cover your customizations, or You need to merge and reapply custom changes onto the new version. Let’s walk through the process using an example and then detail the steps to generate and compare PowerPack reports in SL1. Example Scenario Suppose your team customized PowerPack version 112 and named it 112.1. ScienceLogic has since released version 115. To upgrade your custom PowerPack to a new branch (say, 115.1), you’ll need to: ✅ Compare 112 vs 112.1 to identify what was customized. ✅ Compare 112 vs 115 to identify what’s new from ScienceLogic. ✅ Review release notes for versions 113, 114, and 115 to spot added features or fixes. ✅ Decide which customizations are still needed and merge them into 115.1. Step 1: Generate PowerPack Information Reports SL1 provides a built-in report to list the contents of a PowerPack version. Here’s how to generate it: 1️⃣ Ensure the PowerPack version you wish to report on is installed in your SL1 stack. ⚠️ Important: Do this in a non-production or test environment, as installing older versions may affect data or configurations. 2️⃣ Navigate to the Reports section in SL1. Go to Reports (Navigation Bar). Under Run Report > EM7 Administration, select Power-Pack Information. Choose the specific PowerPack version to report on. Select the Excel format as the output and click Generate. 3️⃣ Save the generated Excel file. 🔁 Repeat this process for each version you wish to compare (e.g., original, customized, and new versions). Step 2: Compare PowerPack Versions Using Excel Now that you have the reports: 1️⃣ Open both Excel files (e.g., 112.xlsx and 112.1.xlsx) in Excel. 2️⃣ If the Developer tab isn’t visible: Click File > Options > Customize Ribbon. Under Main Tabs, enable Developer and click OK. 3️⃣ Under the Developer tab, click COM Add-ins. Check the Inquire add-in and enable it. 4️⃣ You should now see an Inquire tab. Select Compare Files. Choose the two files you want to compare. A Spreadsheet Compare window will open showing the differences. 💡Pro Tip: 🔹 Ignore differences in fields like ID and Edit Date – these are environment-specific and reflect the PowerPack installation date. 🔹 To reduce confusion, consider hiding or removing these columns in Excel before performing the comparison. 🔍 Instead, focus on meaningful differences, such as: Additional or removed objects, including: Dynamic Apps Summary Dynamic Apps Details Event Policies Device Classes Reports Dashboard Widgets Dashboards SL1 Dashboards ScienceLogic Libraries Actions Credentials Changes to version numbers or descriptions for these objects, indicating feature updates or enhancements. This focused comparison helps ensure you’re identifying functional changes rather than irrelevant metadata. Final Thoughts By systematically generating and comparing PowerPack reports: You can clearly identify what customizations were made and what changes the new version introduces. This helps you confidently plan your PowerPack upgrade path and minimize risks. ✅ Review release notes for intermediate versions to avoid duplicating enhancements already included by ScienceLogic. ✅ Always perform this analysis in a non-production environment first. With this approach, you’ll be able to efficiently track PowerPack updates and changes while maintaining your critical customizations.AP2 Dashboarding for "Web Content"
Hi All, I have a Web Content monitor that is aligned to a blank Virtual Device. I want to chart the metrics that are in the Web Content monitor (availability, page size, download speed) in an AP2 dashboard. I'm just trying to get an initial table setup, but will probably setup a line graph later. Right now no matter what I search for in "Metrics and Properties" on the left column, I can't seem to find the Web Content metrics. Does anyone have any tips? Dashboard metric naming seems to be all over the place for some out of the box things. On top of that, just using the basic "Vitals > Availability" doesn't return any data.Best Practices for Device Discovery in SL1
1 MIN READ Effective device discovery is a foundational step in building a robust monitoring environment in ScienceLogic SL1. This guide focuses on best practices when performing manual or guided discoveries via the SL1 user interface. For a full overview of the discovery process, refer to the official documentation: 👉 SL1 Discovery Process Documentation Key Best Practices 1. DNS Configuration When discovering devices by hostname, ensure that DNS is properly configured and functional on the collector. Improper DNS settings can prevent successful device resolution and discovery. 2. Use CIDR Notation Thoughtfully If you're using CIDR notation to define the discovery range: Stick with smaller ranges, such as /24, to limit the scope. Large CIDR blocks can overwhelm the discovery process and slow down the collector. 3. Avoid Overloading the Collector Attempting to discover too many devices in one session can lead to performance degradation. A general rule of thumb (on a medium sized collector): SNMP: Up to 1,000 devices SSH (Linux): Around 500 devices PowerShell (Windows): Around 100 devices 💡 Tip: For large-scale discovery, distribute the workload across multiple collectors or collector groups. 4. Preview Discovery Results Before running a full discovery session, run it with "Model Devices" deselected. This allows you to see what will be discovered without impacting device modelling or performance. 5. Test Credentials First Always use the Credential Tester tool to validate new credentials before launching a discovery session. This ensures that: The collector can communicate with the target devices The credentials are correctly configured and accepted Helpful Resources 🔐 Creating SL1 Credentials 🛠️ Using the Credential Tester ❗ Troubleshooting Discovery IssuesThis week's updates to the Doc sites at docs.sciencelogic.com
5/23/25 Doc updates to the main docs site at https://docs.sciencelogic.com/ The following PowerPack manuals were updated with the following: Monitoring NetApp: ONTAP REST v101 includes a sample credential for guided discovery workflow. Monitoring Dynatrace v200 includes support for version 2 of Entities API. Monitoring Cisco: HyperFlex v106 addresses an issue that occurred during discovery. The Restorepoint 5.6 manual includes updates to add Global Search regular expression functionality and new SAML setup entries. 5/23/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Added release notes for Restorepoint MR20250521 which updates the Global Search page and Global Search API functionality. It also addresses Device Report and archive restoration issues. Added release notes for SL1 Hollywood 12.2.7 and SL1 Ibiza 12.3.4. Both releases include package updates to improve security and system performance and address issues from previous releases. Added release notes for version 108 of the Cisco: Video Endpoint PowerPack release, which includes updates for Python 3 compatibility. Added release notes for version 102 of the Dell EMC: VNX PowerPack release, which includes updates for Python 3 compatibility. Added release notes for the following PowerPacks: NetApp: ONTAP REST v101 includes a sample credential, new Dynamic Applications, and updates for Python 3 compatibility. Dynatrace v200 includes support for version 2 of the Entities API and updates for Python 3 compatibility. Cisco: HyperFlex v106 addresses an issue that occurred during discovery and updates for Python 3 compatibility. Cisco: Telepresence: Endpoints v102 updates for Python 3 compatibility.
Wednesday, May 28th at 11AM ET