Unanswered questions

We're excited to learn more about our attendees! Which of the following best describes your primary reason for attending?  Learn about the future of AI-powered operations  Improve observability and operational visibility  Connect with industry peers and experts  Earn my Skylar One Certification  Learn best practices from customer success stories  Discover new product capabilities and innovations  Advance automation initiatives in my organization  All of the Above!!!  Tell us more! Introduce yourself and share what you're hoping to learn at Nexus Live. 

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.

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

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