Our Aruba Airwave server polls for down Wireless AP's and send traps into Log Manager for each down AP that it finds after every scheduled poll. This means that it sometimes sends multiple traps at one time (one trap for each down AP). The traps all have the same OID, Type, etc, but the entry detail is unique in each trap as it contains the name of the AP which is down. All of these traps reliably arrive in Log Manager as separate entries as they should and each is tagged by a rule which also has alert integration with Orion alerting.
The problem that we are having is with Orion alerting when more than one AP down trap arrives at the same time from the Airwave Server. The issue is that although we can see each trap in Log Manager and the rule has tagged them all, only one of the traps makes it to Orion Alerting. That is a big problem for us as we don't get alerted on all of our down AP's. As an example we had a building lose power and 100+ AP's went down. Log Analyzer correctly showed 100+ tagged entries but Orion Alerting only displayed an alert and notified for one of the AP's and we therefore missed a critical issue as we thought that only one AP was down and therefore we assumed it was not serious.
We opened a case with SolarWinds and they said that the product is working as designed but they acknowledge the issue and the engineer opened a feature request to the development team. To add weight it was suggested I open a feature request here.
This feature request is to therefore please add functionality so that Orion Alerting alerts on all traps when multiple traps are received at the same time from a server/device. This includes where the trap OID, type are the same but the entry detail is different as is the case here.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.