SL1 Hollywood 12.2.4.1 Release Notification
We are pleased to announce that SL1 Hollywood 12.2.4.1 is now available. The release and documentation can be accessed using the following link: https://support.sciencelogic.com/s/release-file/aBtVL0000000V5R0AU/12241 Please note that The SL1 Hollywood 12.2.4 release has been removed from the ScienceLogic Support portal and replaced with the 12.2.4.1 release. This is due to an added security update. 12.2.4.1 release contains additional security updates on top of 12.2.4 release. You can upgrade to 12.2.4.1 directly from the following SL1 versions: 12.2.1.1 12.2.1.2 12.2.3 IMPORTANT: If you are currently on SL1 12.1.2, do not upgrade to 12.2.4.1 until ScienceLogic publishes upgrade instructions in a Knowledge Base article. For full details, please see the SL1 Hollywood 12.2.4.1 release notes: https://docs.sciencelogic.com/release_notes/sciencelogic_12-2-4-1_release_notes.pdfSL1 Hollywood 12.2.4 Release Notification
We are pleased to announce that SL1 Hollywood 12.2.4 is now available. The release and documentation can be accessed using the following link: https://support.sciencelogic.com/s/release-file/aBtVL0000000TbV0AU/1224 The release contains enhancement in Logging and Security updates, and updates in Credentials, Data Collection and Retention, Device Management, Discovery, Events, Monitoring Policies, System Update, and Topology If you are planning to consume SL1 Hollywood 12.2.4, be advised of the following: This release is available only as a patch; there is no ISO version. You can upgrade to 12.2.4 directly from the following SL1 versions: 12.1.2, if all SL1 appliances are running on Oracle Linux 8 (OL8) 12.2.1.1 12.2.1.2 12.2.3 If you are currently on SL1 12.1.0.2 or 12.1.1 and all of your appliances are running on Oracle Linux 8 (OL8), you can upgrade to 12.1.2 or 12.2.1.2 and then to 12.2.4. STIG-compliant users can upgrade to 12.2.4. You must currently be on a version of SL1 with all appliances running on Oracle Linux 8 (OL8) before you can upgrade to 12.2.4. AWS deployments that are using Aurora 3 cannot upgrade to 12.2.4. Users who currently use Python 3.9 execution environments for Dynamic Applications and Run Book Automations should not upgrade to 12.2.4. Due to a known issue, Python 3.9 is not supported in this release. A fix for this issue is planned for version 12.2.5. After upgrading to 12.2.4 and running a security scanning tool against your SL1 appliances, you might experience an issue where the scan lists several "Oracle Linux 8 : container-tools" ELSA security findings. This is due to a known issue that is preventing SL1 from removing certain unneeded packages during the upgrade process for this release. If this occurs, you must perform a manual workaround to remove those packages. For full details, please see the SL1 Hollywood 12.2.4 release notes: https://docs.sciencelogic.com/release_notes/sciencelogic_12-2-4_release_notes.pdf
SL1 Hollywood 12.2.1.2 Release Notification
We are pleased to announce that SL1 Hollywood 12.2.1.2 is now released. You can follow this link to download the release and its documentation. https://support.sciencelogic.com/s/release-file/aBtVL0000000NcX0AU/12212 This version includes modifications of data pull to use JSON, changes to System Updates so that the Database Server or Data Engine are updated first, routine package updates, and package updates to address known security vulnerabilities. For full details, please see theSL1 Hollywood 12.2.1.2 release notes.
Tips for How to Optimize your SL1 System
ScienceLogic SL1 is a very powerful system that can make the lives of your operations staff easier, but those outcomes require some maintenance and optimizations. Read on for a few tips about how to get the most out of your SL1 System 1. Use Event Insights You probably know that Event Insights (Expand left menu -> Events -> Event Insights) is a powerful view to see how SL1 is reducing noise in your system, but did you know that it helps you see potential optimizations also? On the right side of the Event Insights page there is a section called “Tuning Targets”. By looking at what devices are creating the most events and which event policies are resulting in the most events, you can see actions that you can take to clean things up. In the example screenshot above, I would want to look at device 203.0.113.249 to see what is going on to trigger so many events. It could be a misconfiguration on the system, a hardware issue that needs to be remedied, or a threshold that could be tweaked. The lower section shows event policies that are being triggered the most. Noise-reduction options here include requiring multiple triggers within a time frame to be sure that the events are persisting, suppressing the events for test or dev devices, or tweaking thresholds to be sure that the event reflects an actionable problem to fix. 2. Use Operational Insights Operational Insights is a powerpack built by ScienceLogic to help manage your SL1 stack. There are separate versions for self-hosted and SaaS customers, but most of the functionality is the same. Once it’s installed and configured, it presents data on a series of dashboards. These dashboards can help you see the status of your collectors, keep track of the trends in the number of devices discovered and business services configured, and even keep an eye on under-the-hood metrics like Configuration Push time and the Event processing backlog. 3. Daily Health Tasks Did you know that the SL1 Documentation has a list ofdaily health tasks? Some of these items are covered by Event Insights and Operational Insights, but some are not. For example, it’s a great idea to check the System Logs periodically to make sure you know how things are running. If you have concerns about other items in the “Healthy SL1 System” table, you can set event policies and automations to make sure that you are notified in case of any issues. 4. Join the ScienceLogic Nexus Community! Finally, the ScienceLogic Nexus Community is a great resource to keep things working at your best. Interacting with fellow customers, submitting enhancement ideas to the Product Management team, and keeping up with the latest information on new releases helps you plan appropriately and use your time and energy well. To get started: Register with the Nexus Community (its easy) Visit ourCommunity Information Forum for assistance and tips Thanks for your time and I would love to see some feedback and ideas for topics of interest.
