Discussion Forums

 Welcome — Introduce Yourself to the Nexus Community We’re excited you’re here! This thread is a friendly space for Nexus Community members to introduce themselves, connect with peers, and share a fun fact to break the ice. Whether you’re new to the product, a longtime user, an SME, or part of the product team, we’d love to learn a bit about you.What to post (suggested format)Name / Role: e.g., Jane Doe — Site Reliability Engineer Company / Team: optional How you use Nexus: short summary — monitoring, incident response, dashboards, automation, etc. Something fun: a hobby, favorite snack, a weird skill, or a memorable travel story — keep it light! One thing you’d like to learn from the community: topic, tip, or resource requestExample introductions (copy and modify)Hi everyone — I’m Alex (SRE). I use Nexus to correlate performance signals across our multi-region services. Fun fact: I’ve completed three half-marathons. Happy to share dashboards and alert tuning tips!Hey all — I’m Priya,

Hi to all, we configured a Global Manager in our QA env for 2 stacks but there is something that it's not really clear to me.The global manager is not capable to manage PP on the stacks (in AP2 UI there is any menu entry for PP), is not capable to retrieve device groups defined on the stacks, is not capable to retrieve device class from the stack, is not possible create device groups and add devices monitored by the stacks.My first question is: how can we create a dashboard that can filter panels based on custom device group?

Using version 104 of the Power Pack in Linux queues other than the Transmission and Dead Letter queues have to be listed within the snippet. In a large account with 100’s of queues this is really not feasible to maintain.  Other queues should have the ability to be added by type such as Local Queues or by using wild cards or Regex in the snippet.

Hello Community,We have a requirement to automatically discover newly created queues within an already monitored IBM MQ Queue Manager.Currently, when a new queue is created, the queue name must be manually added to the discovery snippet before SL1 can discover and monitor it. In environments where queues are created frequently, this creates additional operational overhead and increases the risk of queues not being monitored until manual intervention occurs.Requested EnhancementAutomatically discover newly created queues under monitored Queue Managers. Detect new queues during scheduled discovery/re-discovery cycles. Automatically create queue components and apply existing monitoring policies. Support include/exclude patterns to control which queues are monitored. Eliminate the need to update discovery snippets whenever queues are added.Use CaseOur MQ environment is dynamic, and new application queues are introduced regularly. Having to manually maintain queue names in the discovery con

Hi Team,  We need to have flexible options in behavior page to select as per our need . We need to have all the above four option as a drop down box in behavior page to selection as per our wish, as of now it is limited only to Collection and processing Enabled . 

We have been dealing with unknown behavior in our ScienceLogic Environment, and we would like to explain point wise to keep it clean.Application Team has reported us that File system Unavailable events are landing in their SNOW queue in the form of ticket. We have investigated and File System unavailable major events have been triggered. Furthermore, we have navigated into Registry » Hardware » searched with specific server name to find out reported File System have been discovered or not. We have found that those are not discovered and when connected back to the application team. we have got two types of inputs. 1st » multiple File System unavailable event are trigger for user profile for example /home/baljeets [whenever user log into Solaris Server. there profile will be created and once they logoff from the server FS related to their profile will be unmounted and ScienceLogic triggers major] 2nd » backup job will be triggering time to time and once the backup job is complete. same k

Greetings, Nexus Community Members! We are excited to extend an invitation to all of you to engage with us in a fun and meaningful way. This is a perfect opportunity to get to know some of our team members and, more importantly, for you to share a bit about yourselves. Meet the Team Our team is dedicated to making Nexus a thriving community where everyone feels welcomed and inspired. Each member brings unique skills and passions to the table, and we can't wait for you to meet them! From tech enthusiasts to creative minds, we all share a common goal: to support and uplift this amazing community. Cheers!  Sara- Nexus Community Manager

I am looking for advice/help on monitoring Cisco Nexus 9000 Series switches.  The metrics the business is asking to monitor are: Metric   CPU Utilization   Memory Utilization   Device reload Alert   Interface errors (ifInErrors and ifOutErrors) (CRC, FCS)   Interface Discards ( ifInDiscards and ifOutDiscards)   Interface status   Utilization Bandwidth   PSU status   Fans   BGP/OSPF status   SNMP availability   TCAM Utilization monitoring (working to get MIB/OID from Cisco)   MAC Table Exhaustion  

The vEdge Container availability check does not currently validate vManage REST API availability. Because of this limitation, the vEdge Container can remain available even when API-dependent vEdge devices, which are child components under the vEdge Container, are impacted. This prevents topology-based event suppression from working as expected and can result in multiple child component availability alerts for a single API-related outage.Proposed Enhancement: -Enhance the vEdge Container availability logic by adding an availability check via the vManage REST API. If the API is unavailable, the vEdge Container should also fail the availability check and move to an unavailable state.Expected Behavior: -When the vManage REST API is unavailable, the vEdge Container should fail its availability check. The vEdge Container should be marked as unavailable before the child vEdge devices generate individual availability alerts. Topology-based event suppression should suppress availability alerts

For powershell devices, when a device is first discovered, the cred used to added into this cred keys table, and then nightly discovery will also use that cred. You can also add a second cred from the properties page. The issue i found is that if you change creds, for whatever reason the cred key table doesn’t get updated. We have created a DA which dynamically aligns DAs using ‘from sl_credentials.constants import CRED_POWERSHELL’ to pull the credentials. because its not updated the DA doesn’t work Is there a way to pull the credential for a powershell device more dynamically, also, i think the nightly discovery also uses the same, so I think that it would also fail?Or is there a process which updates the table? 

We would like to get an update for following disclaimer for on Linux Base Pack v114. Reason being, it has been almost 5 months, and it has not been update on SL Support Portal ** We are currently reviewing a potential performance-related issue that we have identified internally with Linux Base Pack v114. We will provide an update on next steps once our evaluation is complete. **

I recently created a Runbook Automation/Action whose job it is to set newly discovered components to a different Organization. It triggers off the “Component Device Discovered” Event Policy.I ran into a handful of the following errors when a group of Aruba APs was added to Central around the same time:Snippet (723) failed to execute with exception: Failed to acquire lock /tmp/envmanlock-83EF68E00F35226911E02C49561FADFA within 60 secondsResult:NoneThis particular Aruba environment is known for how big it is, so there could be some issue with volume of devices getting discovered at the same time, but is anyone familiar with the error and why it could be happening?

I am sending events to the SL API to create an Event with ‘Use Message-match’ enabled. Sometimes the source will send events to the API which would just have a issue ID changed, but relating to the same event.  For example. First post: Issue: broken ID: 39393Second post: Issue: broken ID: 53291 I want SL to group the events based on the issue, at the moment it would create a new event.  This is my regexpartner=(.*?),sndinterface=(.*?),resourcetype=(.*?),rcvid=(.*?),rcvinterface=(.*?),status=(.*?),glbID=(.*?) In essence, i want SL to ignore the last field (glbID) when it tries to match the events.  Is this possible? Thanks  

It has been observed that SNMP credentials (such as community strings, SNMPv3 authentication/privacy keys, and SSH credentials) are retrievable in a readable format through authenticated API access.This behavior represents a significant security vulnerability, as sensitive credentials should never be exposed in plaintext. If the exposed credentials have Read-Write privileges, an attacker who gains API access could potentially modify device configurations, disrupt services, or compromise the integrity of managed systems.As a security best practice, all sensitive credentials should be encrypted at rest and should not be retrievable in a user-readable format through any API response. Where credential validation is required, mechanisms such as secure storage, tokenization, hashing (where applicable), or masked values should be implemented instead of returning the actual credentials.We recommend remediating this issue by ensuring that sensitive credentials are securely encrypted and inacces

Two recent Cisco Unified Communications Manager advisories — one an actively-exploited zero-day — can be scoped today using data the CUCM PowerPack already collects. 1. SummaryCisco has disclosed two vulnerabilities affecting Unified Communications Manager. If you monitor CUCM with ScienceLogic AI Platform, you already hold the two data points needed to scope exposure: each cluster's running software release, and which services (including WebDialer) are active.CVE Type Severity Status CVE-2026-20045 Remote code execution via the web management interface, no authentication required CVSS 8.2 Critical (SIR) CISA KEV Actively exploited in the wild CVE-2026-20230 Server-side request forgery (SSRF) that can escalate to root CVSS 8.6 Critical (SIR) PoC code available; no confirmed in-the-wild use. Conditional — see note.  Why "Critical" with a sub-9 score? Cisco assigns both a Security Impact Rating of Critical — higher than the numeric CVSS suggests — because successful

Hi All,  As of now all the filesystem for SL1 data collector and message collector type is showing as other where monitoring of FS is disabled at default. The Appliance must be customized to make  valid type so that this will not be hidden at default. 

Hi ,  Whether SL1 does has the Intelligence  to detect the parent and child relationship based on CDP and LLDP information . If it works means can you let us know how device is picked as parent and child. 

Hi All,  We have most of devices enabled with CDP and LLDP , if we see the view in the map the both the devices are connected to each other in view which is not helpful . Device A is parent and device B is child , But in maps both the device is showing as parent as well child. Whether everyone has this issue ?  

The process Process 'Update Device State' has a default frequency of 1 min, but we have a large number of device groups, over a thousand, i see this every minute 'already running, not starting, proc name Update Device State' And after a few minutes it then sends a signal 15, and terminals the process 'Process Update Device State has caught signal 15 and is exiting.'I'm wondering whats the implications if i change the time factor to allow the process to run longer, or if there is an limitation to the number of device groups that should be allowed?     

Hi All, Anyone upgraded the Skylar one to 12.5.1 ? Looks like the new feature Enhanced Topology process is not working for us .. is it for anyone else as well?

The issue about the Yum RPM DB Corruption. Thread died in Berkeley DB library. Fatal error, run database recovery” has been a bit frequent on the OS level (I understand this is not something related to the platform support). The occurence of this issue is ideally resolved with the help of KB https://support.sciencelogic.com/s/article/8821 . But, I was looking if there ia  way to alert on this and be aware something broke instead of being silent on this.

We believe that our Concurrent powershell collections are running into some security software we have running on 0, 5, 10, 15, 20, etc minutes. We wanted to try to offset ScienceLogic Powershell to run on 2, 7, 12, etc if possible.I am familiar with System > Settings > Process > Data Collection: Dynamic App… I changed this one to offset by 2 which worked for non Powershell collections but didn’t work for Powershell… I also found “Data Collection: PowerShell Collector”, but this process does not have an offset setting.