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.
How to Fix powershell communication error?
How to Fix powershell communication error Forward and reverse name resolution is not properly configured for server? We have multiple windows server in which we are facing this issue and server have multiple DNS entries and we can delete them. also i tried to add IP and host in sciencelogic data collector also added in dnsmsaq-resolve.conf to resolve this issue but still we are facing this error Forward and reverse name resolution is not properly configured for server, how to fix this issue without deleting DNS entries.
