SNMP Traps and Syslog Traps can raise an advanced alert in NPM

guys.  this  require something called bus for messages .... in OSS terminology (this inputs like snmptraps/syslog/exports) are  called northbound, and southbound interface...  honestly i am pretty dissatisfied with currrent progress on this topic...  i am courious, if there is somebody from solarwind emp. who is reading it .. this basic feature is discussed here since ages... this must be core feature of solarwinds...and still we are opening new and new feature requests, and all are(and problably will be ) neglected by solarwind PM team

I, uh....what?

I get you don't like this and it does need improvement, but this isn't one that is entirely neglected. They literally put in framework to update it accordingly via introducing rabbitMQ - which on the long term enables a variety of methods to handle the issue.

ok. sory for negative comments. but i work with solarwinds since years, and having serious troubles due to this. hope it will be avaiable fast. cheers.

ok. sory for negative comments. but i work with solarwinds since years, and having serious troubles due to this. hope it will be avaiable fast. cheers.

I think it's fair to say that a lot of things need improvement and their teams may be a bit too stretched, but at least this one they *are* working on. lol.

I suspect they won't implement this obvious/useful feature not because it's technically difficult to do so, but because by enabling users to generate alerts based on SNMP traps reduces dependence on monitoring ports, and Solarwinds' charges per port. In order words, by implementing this feature they could end up losing money. If you go back through the forums, people have been asking for this for years.... why haven't they implemented it yet? They probably never will.

It's a real shame because there are all sorts of critical events that generate SNMP traps, but we can't do much with them with NPM, other than log them or generate emails.

Even if the event can be picked up through SNMP polling, we have to wait until next polling interval before we are alerted to this (maybe 15/30 minutes).

Also, if the status of some device on the network changes, and changes back to how it was within the polling period, Solarwinds may never even become aware of the incident.

An event may have occurred, or it may not, who knows??? Not exactly suitable for mission critical situations Solarwinds.

A serious downside to Solarwinds NPM!

Thanks,

Bruce.

It's going to be ugly when I tell a new customer is not is not possible. They just spent a ton of $ and I'm going to look friggin' silly. Ugh.

Really orioncrack - it is very ugly when management is asking something to improvement in infra monitoring part and as an implementer, we are always saying one thing this feature is not available or this is under feature request, totally bad impression,

now every one start to suggest use this and that tool, same will give you the correct picture.