Is anyone else running SL1 v12.1.2?
We were supposed to be upgraded to v12.2 but problems with Aurora (the AWS database offering) we have ben placed onto v12.1.2. We were handed the system on September the 9th, and the release notes are dated the 10th. It has zero backward compatibility with collectors (all must be on 12.1.2) and we've been plagued with critical system alerts before we even attached a collector. I kind of get the feeling that we're alpha testing this release.... ☹️ Can anyone else, give me some comfort and confirm that we are not the Guinea Pigs for this release?
Which Dynamic App is more efficient for Linux File System exceeds a threshold
Which Dynamic Application is more efficient for File System Utilization SL1 can trigger two different type of events for when a File System exceeds a threshold: File System exceeded events are generated via an Internal DA by SL1 and is executed every 5 minutes Host Resource Storage Utilization events are generated via a Discovered DA from the SNMP agent on the host and can be collected at 5, 10, or 15-minute interval I am trying to determine which one make more sense to use on linux servers and is not as taxing the data collectors.Overlapping IP addresses
This might be an oldie... How should we manage devices which have multiple overlapping IP addresses. For example Layer3 switches or router HA pairs can have same IP addresses set up to two or multiple devices for routing high availability or management reasons. This then makes SL1 see same IP addresses in multiple devices. And that then generates events into System organization, events like: A Message Collector is managing multiple devices with an overlapping secondary IP address: Secondary IP address overlap on devices managed by Message Collector: 101 | Collector Groups: 44 | IP Address: 128.0.0.127 | Device IDs: 70999, 70998, 71001, 71009, 71005, 71003, 71006, 71004, 71007, 71002, 71013, 71012, 71015, 71010, 71014, 71008, 71016 Ok, that IP address can be deleted from database, but the nightly discovery again brings up the same issue next day. And because those are network devices where every now and then are some changes done in interfaces I believe we just have to have the Auto-Update enabled for those devices. So: is there a way to tell that please do not discover all IP addresses for this device is there a way to make SL1 accept that, some other way than creating pretty interesting regexes into event policies event policy is for system level so that not easily be just suppressed for some devices are there some other ideas how to manage this situation
Need a help on Low ode Information
Hi Everyone I am currently trying to gather information about low-code in ScienceLogic, including how it works, what updates and changes have been made, how it can be implemented, and how we can effectively use it. If anyone can provide related documents or resources, it would be very helpful for me
Support Video: Event Management Overview
Following this video, learners will be able to: Know more about specific features such as viewing events, acknowledging and clearing events, understanding the way events are ranked on the event console, finding out more information about each event, and how we can automate actions to address particular events.
Who will be our next SL1 Innovators?
Hello Nexus Members, Looking to showcase your creativity, innovation, and inspiration? Look no further. In case you're opted out of email, we just launched our SL Innovators Awards!! Our ScienceLogic Innovators Awards were established to recognize and learn from those nerdy by nature, tech buffs, and visionaries using SL1 in pioneering ways to power a better way to work. Show the Nexus Community something cool and innovative you've been working on to achieve real business outcomes. We want to hear your ideas! Submit your applicationby September 12.
