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
Featured Content
Recent Content
Oracle: Database v200 PowerPack Release Notification
We are pleased to announce that the Oracle: Database v200 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/aBu4z000000Xa2QCAS/oracle-database Enhancements and Issues Addressed The following enhancements and issued addressed are included in this release of the PowerPack: Removed the following dependencies to improve the discovery process for Oracle devices: tnsnmanes.ora smon process pmon process Listener status parsing OS informations oratab (for Linux servers) Refactored nearly all Dynamic Applications to eliminate cache dependencies, enhancing overall system reliability and performance. Removed support for the following SOAP/XML credential headers: SID:PORT TNS_ADMIN GRID_PATH HOST TYPE_OF_OS Updated the Collector Affinity from Root device collector to Assigned collector. Modified the PowerPack so Windows users no longer need a PowerShell credential. Maintained support that Linux users must still use the SSH credential for the following Dynamic Applications: Oracle: DB Archived File System Stats Oracle: DB Non-Archived File System Stats Added support for Oracle Database version 23ai. Made the following updates for the "Oracle: DB Server Config" Dynamic Application: Removed the cache dependency Updated the discovery object Renamed the "OS Type" collection object to "Port String" Removed the following collection objects: Oracle DB Status DB Name UUIDAvailable OS Version Server Config Listener Lookup PMON Lookup ASM Lookup Oratab Lookup Oracle DB Config Lookup Status SMON Lookup RAC Lookup Made the following updates for the "Oracle: DB Instance Discovery" Dynamic Application: Removed the cache dependency Removed the "RAC Status" collection object Renamed the following collection objects: "Instance Config" to "Database-Level Information" "Listener Host" to "Database Created Date" "Listener Names" to "Database ID" "Instance" to "Database Name" "Instance Status" to "Database Open Mode" "Listener Port" to "Database Role" "Oratab Entry" to "Database Unique Name" "Listener Config" to "Instance-Level Information" "Listener Name" to "Instance Hostname" "Listener Instances" to "Instance Name" "Listener Log File" to "Instance Startup Time" "Listener Parameter File" to "Instance Status" "Listener Protocol" to "Instance Version" Made the following updates for the "Oracle: DB Instance Config" Dynamic Application: Removed the "Instance Reachable" collection object Added the "ASM Installed" collection object Removed the following alerts and events: Oracle: DB Instance Connection Status Reachable Oracle: DB Instance Connection Status Unknown Oracle: DB Instance Connection Status Unreachable Updated the "Oracle: DB Log Alerts Config" Dynamic Application to align to CDB Oracle Database instances. Made the following updates for the "Oracle: DB Data Guard Gap Stats" Dynamic Application: Modified the Dynamic Application to only collect if the Oracle database has the parameter dg_ broker_start set to TRUE Simplified the query to improve performance of the Dynamic Application Renamed the following collection objects and presentation objects: From "Gap to Primary" to "Thread" From "Gap Received" to "Last Sequence Received" From "Gap Applied" to "Last Sequence Applied" From "Standby DB" to "Name"Made Made the following updates for the "Oracle: DB Resource Stats" Dynamic Application: Renamed the following thresholds: From "Process Utilization Critical" to "Process Utilization Percent Critical" From "Process Utilization Major" to "Process Utilization Percent Major" From "Session Utilization Critical" to "Session Utilization Percent Critical" From "Session Utilization Major" to "Session Utilization Percent Major" From "Transaction Utilization Critical" to "Transaction Utilization Percent Critical" From "Transaction Utilization Major" to "Transaction Utilization Percent Major" Added new thresholds: Process Utilization Percent Minor Session Utilization Percent Minor Transaction Utilization Percent Minor Renamed the following alerts: From "Oracle: DB Process Utilization exceeded critical threshold" to "Oracle: DB Process Utilization % exceeded critical threshold" From "Oracle: DB Process Utilization exceeded major threshold" to "Oracle: DB Process Utilization % exceeded major threshold" From "Oracle: DB Process Utilization has returned to normal" to "Oracle: DB Process Utilization % has returned to normal" From "Oracle: DB Session Utilization exceeded critical threshold" to "Oracle: DB Session Utilization % exceeded critical threshold" From "Oracle: DB Session Utilization exceeded major threshold" to "Oracle: DB Session Utilization % exceeded major threshold" From "Oracle: DB Session Utilization has returned to normal" to "Oracle: DB Session Utilization % has returned to normal" From "Oracle: DB Transaction Utilization exceeded critical threshold" to "Oracle: DB Transaction Utilization % exceeded critical threshold" From "Oracle: DB Transaction Utilization exceeded major threshold" to "Oracle: DB Transaction Utilization % exceeded major threshold" From "Oracle: DB Transaction Utilization has returned to normal" to "Oracle: DB Transaction Utilization % has returned to normal Added new alerts and events: Oracle: DB Process Utilization % exceeded minor threshold Oracle: DB Session Utilization % exceeded minor threshold Oracle: DB Transaction Utilization % exceeded minor threshold Made the following updates for the "Oracle: DB RAC Flash Recovery Stats" Dynamic Application with the following: Added a new threshold: Flash Recovery Usage Minor Added a new alert and event: Oracle: DB RAC Flash Recovery Usage exceeded minor threshold Renamed the "Oracle: DB Tablespace Stats" Dynamic Application to "Oracle: DB Tablespace Datafile Stats" and addressed an issue related to data collection and alerts. Added the new "Oracle: DB Overall Table Stats" Dynamic Application. Added two new collection objects to the "Oracle: DB Tablespaces and Datafiles Status Config" Dynamic Application: Tablespace Autoextensible (Group 1- If the tablespace has autoextensible datafiles) Autoextensible (Group 2- If the datafile is autoextensible) Added the new "Oracle: DB Instance Device UID Update Required" run book automation and "Oracle: DB Instance Device UID Update" run book action to update unique identifiers on Windows devices. Updated the following Dynamic Applications to align to the root device rather than to the CDB/PDB if the Oracle device is a RAC instance: Oracle: DB RAC Disk Group Space Stats Oracle: DB RAC Flash Recovery Stats Oracle: DB RAC Global Cache Stats NOTE: After updating the PowerPack to version 200, ScienceLogic recommends manually unaligning the RAC Dynamic Applications because they might remain aligned at the CBD and PDB level after updating. Then you must run the discovery session again or manually align the RAC Dynamic Applications to the root device. Otherwise, they will be aligned during nightly discovery. Removed deprecated Dynamic Applications: Oracle: DB ASM Diskgroup Config (moved) Oracle: DB ASM Instance Config (moved) Assigned the "Oracle Database: Instance" device dashboard to the following device classes: Database Container Instance Database Instance Database RAC Instance Database Server Pluggable Database Removed the following API Event Policies: Oracle: DB Could not find SID instances in oratab Oracle: DB failed to get SERVICE_NAME details from the server Oracle: DB instance listener is down Addressed an issue that prevented the "ASM" Dynamic Applications from collecting data when the database credential contained the value %D. Addressed an issue that caused messages about the obsolete "Oracle: DB ASM Dynamic Application Alignment" run book action to be logged on the Database Container Instance device. Addressed an issue that caused non-container instances to retrieve alerts from other instances. Addressed an issue that prevented Oracle devices with Native Network Encryption (NNE) enabled from aligning to Dynamic Applications. Decreased the number of sessions created by the PowerPack by 68% which contributes to improved system efficiency. Please refer to the Oracle: Database v200 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Oracle: Database v200 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Oracle: Database v200 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report.Linux Base Pack v113 PowerPack Release Notification
We are pleased to announce that the Linux Base Pack v113 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/aBu0z000000XZHFCA4/linux-base-pack Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Updated the PowerPack for Python 3.11 compatibility and to use the latest gevent library. Addressed an issue that prevented the "Linux: ICDA Cache" and "Linux: Interface Cache" Dynamic Applications from processing interfaces without MAC addresses. Added the following new Dynamic Applications: "Linux Memory Pressure Performance" Dynamic Application. "Linux: Large Open Files Configuration" Dynamic Application. NOTE: After you update to version 113, the "Linux: Memory Pressure Performance" and "Linux: Large Open Files Configuration" Dynamic Applications will not automatically align. If you want to monitor memory pressure or Open files, ScienceLogic recommends that you align them manually or use the template. Added a new "CPU Work Utilization %" presentation object to the "Linux: CPU Performance" Dynamic Application. Please refer to the Linux Base Pack v113 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Linux Base Pack v113 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Linux Base Pack v113 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report.Poly Endpoint v103 Py3 PowerPack Release Notification
We are pleased to announce that the Poly Endpoint 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/aBu0z000000XZfMCAW/polycom-endpoint Enhancements and Issues Addressed As this PowerPack has low usage relative to other integrations, ScienceLogic has limited access to test environments for this technology. ScienceLogic would like to invite users to assist in validation of the latest version, v103, of this PowerPack which implements Python 3.6. Please reach out to your account team to gain access to the latest release. The following enhancements and addressed issues are included in this Limited Availability release:: Updated the PowerPack for Python 3.6 compatibility. Renamed the PowerPack to "Poly Endpoint" PowerPack. Please refer to the Poly Endpoint v103 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Poly Endpoint v103 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Poly Endpoint v103 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Poly Endpoint v103 Py3 PowerPack Release can be found in the Release NotesInterface admin/operationally down events
OK. So I'm fairly new to modifying events in SL1, but our NOC has requested that we research suppressing the "Poller: Interface operationally down" event if "Poller: Interface Admin down" is active on a given interface. That makes perfect sense to me. If an interface is admin down, then there is absolutely no need for the operationally down event/alert. Other tools I have administered in the past had this logic baked in out of the box, but that doesn't seem to be the case with SL1. I looked at using the Autoclear option for the Admin down event to have it clear the operationally down message, but I'd much rather just not have the operationally down event trigger at all if the interface is admin down. Any thoughts on how to get this configured? Thank you.This week's updates to the Doc sites at docs.sciencelogic.com
6/27/25 Updates to the main documentation site at https://docs.sciencelogic.com/ : Updated the Skylar Analytics manual with additional steps for creating and customizing dashboards and charts in the Data Visualization component. Updated the Organizations & Users manual with a more detailed description of how role-based access control (RBAC) determines the features and content that users have access to in SL1. 6/27/25 Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ : Added Release Notes for the Cisco: Intersight v102 PowerPack, which updates the PowerPack for Python 3 compatibility. Added Release Notes for the Dell XtremIO v106 PowerPack, which updates the PowerPack for Python 3 compatibility. Added release notes for Skylar Analytics 1.6.1, which addresses issues with duplicate tables and metrics. Added release notes for version 111 of the Cisco: UC VOS Applications PowerPack release, which includes updates for Python 3 compatibility. Added release notes for version 8.20.70-45 of the AP2 Lokma release, which includes several updates to the Business Services, Devices, and Event Policy Editor pages.
Dell EMC: XtremIO v106 Py3 PowerPack Release Notification
We are pleased to announce that the Dell EMC: XtremIO v106 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/aBu0z000000XZXDCA4/dell-emc-xtremio Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: The PowerPack was updated for Python 3.6 compatibility. Please refer to the Dell EMC: XtremIO v106 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Dell EMC: XtremIO v106 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Dell EMC: XtremIO v106 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Dell EMC: XtremIO v106 Py3 PowerPack Release can be found in the Release Notes
