sciencelogic platform

13 Topics

Welcome to the ScienceLogic SL1 Discussion Forum
We would like to welcome you to this forum where you can participate in open collaboration and meaningful discussions about all things SL1. The purpose of this area is to foster collaboration about ScienceLogic SL1 topics and ideas and for you to find solutions. As a community of IT professionals, we're always eager to learn new things and improve our skills. In this forum you can find people with similar ideas and challenges who can help you learn and be inspired. We hope you look forward to participating in these discussions and contributing to the community. Cheers to fostering connections, sharing insights, and driving the future of AIOps together. The ScienceLogic Community Team
SaraLeslieAdmin
6 months ago Place ScienceLogic SL1
74Views
7likes
0Comments
Group rules for Interface
Hi All, There is any plans from to implement the grouping for interfaces .i:e I need to group the interface where the alias name contains or starts with MSP . Basically this will help for reporting , dashboarding and applying template only to specific set of interfaces.
Solved
Issac
4 months ago Place ScienceLogic SL1
42Views
2likes
2Comments
Automatic Rebalance of collectors
There is any plans from SL team to make automatic rebalancing of collector groups in certain interval like 24 hrs once.? As of now its needs a manual intervention.
Solved
Issac
4 months ago Place ScienceLogic SL1
79Views
2likes
8Comments
2024 Customer Success Honoree Award Winners
Any community whether online or in person is a place to share and learn. As leader of Customer Advocacy, my role too encompasses sharing the voice of our customer in many formats in order for our peers to thrive from this knowledge. In case you missed it, we recently launched our ScienceLogic 2024 Customer Success Honorees - an awards program recognizing those who have made significant progress in a specific area, and have been an integral champion for SL1 success. I wanted to share with you these wonderful advocates, our finalists, in the hopes it inspires you to share your stories of success with our new Nexus community! Stay tuned for our upcoming 2024 Innovators Awards, an application-based awards program celebrating and recognizing customers and partners who are leading the charge in digital transformation, operational excellence, innovation, and business impact utilizing SL1 in innovative ways. Applications are opening early June! Read more in our CS HonoreeeBook. Congratulations to each of our 2024 Honorees! 👏💣 If you're interested in telling your SL1 story, please reach out to me, and join our Pathfinders customer advocate program.
kyraecker
5 months ago Place Community Information
26Views
2likes
0Comments
Extend Internal Interface collection
Hi All, As a default Sl1 is polling the interfaces with limited metrics , if i need to add few metrics additional is is possible to extend the internal collection? Basically i don't want to create a new DA and poll the interfaces for the limited metrics , with the same poll cycle i need to capture the additional details.
Solved
Issac
6 months ago Place ScienceLogic SL1
194Views
2likes
6Comments
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
teppotahkapaa
2 months ago Place ScienceLogic SL1
43Views
2likes
2Comments
Event Policy expiry delay during outage
Hi All, What happens when collectors has an communication issue with central database for more than 2 hrs , because we have some event policy set to expire if the event didn't rigger for 60 mins . During this network outage the existing alarms will be cleared if the collector doesn't send update about its polled devices?
Solved
Issac
5 months ago Place ScienceLogic SL1
61Views
1like
2Comments
How Do I Set The Parent Device Of A Device?
Hello, I hope someone can assist with the following. I am using Device Component Mapping to create a hierarchical/tree structure of devices, but SL seems to assign the Parent Device attribute randomly for each device created, and I need to be able to set the Parent Device correctly, so that the hierarchical structure is correct. I have data that contain a set of locations that correspond to the tree structure. The structure has this concept: One Country -> Many Cities -> Many Buildings -> Many Rooms. Each data record has an id, a name, a parent id and a type. The data is split into cities, buildings and rooms. For example, a city record might be as follows: id: CITYPARIS, name: Paris, parent id: CTRYFRANCE, type: city. A building record might be as follows: id: BLDGMONTPARNASSE, name: Tour Montparnasse, parent id: CITYPARIS, type: building. And to complete the picture, a room record might be as follows: id: ROOMMEETING1, name: Meeting Room 1, parent id: BLDGMONTPARNASSE, type: room. When I create one of the 'tree' levels of devices (it could be city, or building, or room), in my Dynamic Application, the code snippet extracts cached data where the type is 'city', then passes the extracted data to the result handler, which populates the four collection fields: id, name, parent_id, type. The id field is set to be the Unique Identifier, the name field is set to be the Device Name, and the type field is set to be Class Identifier 1 (I've created device classes for each tree level, allows me to have funky icons to distinguish the devices visually). The DA then creates devices for each record found, and I see them appearing on the Device Manager screen. However, when I examine each device, the Parent Device that is set seems to be random. For example, three city devices created (Paris, Nantes, Poitiers) all were assigned a Parent Device of 'Paris', the name of one of the devices created, instead of using their own parent_id values. Is there a way to tell SL what the Parent Device for each device record should be, perhaps in the snippet or somewhere else? Can I use one of the field values extracted from the cached data (ideally, my parent_id) as the value for the Parent Device field? This is my first post here, so apologies if this is in the wrong place!
Solved
TADAndyMarshall
2 months ago Place ScienceLogic SL1
133Views
1like
14Comments