-----Original Message----- From: Orangepeel Beef <[email protected]> Reply-To: rsyslog-users <[email protected]> Date: Tuesday, April 8, 2014 at 2:24 PM To: rsyslog-users <[email protected]> Subject: Re: [rsyslog] Rsyslog w/ logstash-elasticsearch-kibana server
>imho you want to go the redis route when you need multiple indexers to >read >the same stream of data. my rsyslog collectors are also my logstash >indexers, so no need for the intermediary layer. > >or, when you can't get syslog data directly and need redis to distribute >your data to logstash from anywhere. FWIW this is what we do, but with RabbitMQ. We have multiple indexers to keep up with volume, and also went this route because we're using federation hubs/spokes for persistence vs relaying alone. This is one reason I need to PoC vs rip/replace, to determine if I want to try (or even can) integrate rsyslog with RabbitMQ in some way (even if it's a hack for now, and perhaps a sponsored feature request down the road) or completely rework the existing architecture and use disk assisted queues (or something) to mimic what's done with RabbitMQ today. _______________________________________________ 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.
