On Mon, Nov 4, 2013 at 2:23 AM, Jacob Steinberger < [email protected]> wrote:
> Honestly, I'd kick in a few bucks for this out of my own pocket (SNMP > receiver/forwarder). > > The problem with snmptrapd is they added a feature which requires you to > list what community strings you want it to process/forward. If you're in a > large environment and have no control over the edge devices, there's no way > to use the product like that. You just can't know all the community strings. > Actually, the presence of that snmptrapd tool always made us think that there is no point in writing a native input for rsyslog. So that's a prime reason that only the SNMP output is there. > Sure, you can say something like "Standards!", or "Best Practices!", but > we all know that some days they're just words to some people ... > > To have a respected, concrete product like rsyslog provide this ... like I > said, I'd kick in a few bucks. > > While I need to sell this internally, I think we could get this SNMP piece done as part of such a quick job. If folks would really commit to $600, I would try to drive this forward. On Netflow: that's unfortunately something thats *far* beyond the scope of these simple jobs. We would need to do a real estimate, but it's in a different ballpark. Sorry I have no better answer, I personally would also love to see it... (but keep on your mind that Adiscon's core business is developing software (and consulting/support along that), so there is no "big project" that otherwise funds development). Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
