Seeing people referring to "REK" made me smile this morning. We've been referring to our setup as REK for quit awhile - http://www.meetup.com/RVA-Data-Hackers/events/214996202/
I don't really see a reason for redis in the equation unless it's already part of your infrastructure though. imkafka is potentially interesting however. I wrote imczmq for rsyslog so I have a little experience writing input plugins - if there are others with a need for a such a thing that would be a fun collaboration. Brian On Wed, Nov 23, 2016 at 6:52 AM Bob Gregory <bob.greg...@made.com> wrote: > There've been a few discussions over the last few days that are all > pointing in the same direction: > > * Is it better to use Rsyslog's omelasticsearch rather than pushing to > logstash? > * Should we have a minimal log shipper component as distinct from rsyslog's > processing capabilities? > * Ought we to have an imhiredis module? > > Really what we're talking about is replacing Logstash (and the various > beats) with rsyslog. I'm perfectly happy with that, Logstash is a > resource-expensive and fickle beast that spoils my otherwise pristine log > pipeline, but I do think the community ought to think about whether this is > the direction they want to take. > > For my part, I'm quite happy to help build an imhiredis (and imkafka?) > module but only if I can actually dogfood it, which means replacing > Logstash in our own environment. > > For that, I'd like to see better support for GeoIP tagging, a Riemann > output plugin, some better guidance on "failed message queues", etc. etc. > etc. > > Are we jointly interested in building the REK stack and, if so, can we > start to work out the feature set we're missing, and the documentation we'd > need for this to work? I'm a little concerned that if we tackle the usecase > piece-meal, we'll end up with lots of disjointed parts that don't really > solve the problem: logstash is not an adequate logstash. > _______________________________________________ > 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. > _______________________________________________ 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.
