Trap Threshold in a Event Policy
Hello SL community, I'm trying to create some events based on traps received. Some of the policies require a threshold to match an event. For example, the "tempOfSensor:" string should trigger a Critical event if the value is between 60 and 65. Is there a way to include a range of values in a trap-based alert, using either the result of an OID or a value inside that trap? Something similar to what we can do with a Dynamic Event Source.Suppressing Specific BGP peers
There's been a number of times where we have come across customers who have BGP peers that are not in use or sporadically in use, but they do not wish to remove it from their configs. As a result we get perpetual alerts, but we cannot suppress them as the event suppressed would prevent all bgp peers from alerting. Anyone have thoughts on some ways to single out peers that can be ignored on a per device level? Side note: We are using Powerflow and ServiceNow so we can possibly do something in the path as well. ServiceNow could take care of it, but doesn't help with the peers that flap.
