[rabbitmq-discuss] RabbitMQ + Logstash + Rails

Tue Oct 30 22:07:31 GMT 2012

I'd highly recommend asking on the #logstash irc channel on freenode.net.
The lead dev's nick is whack and he's very responsive to questions.

I'd hazard a guess that the answer to your questions "why have an agent on
every machine?" and "why not send everything over AMQP?" really boils down
to your requirements.

On 31 October 2012 08:39, Alexis Richardson <alexis at rabbitmq.com> wrote:

> You might also want to ask this on the ruby gem list...
>
> On Tue, Oct 30, 2012 at 6:05 PM, Mark <static.void.dev at gmail.com> wrote:
> > Anyone out there using RabbitMQ with Logstash and/or Gralyog2? If so,
> could you please describe your experiences.
> >
> > General questions about the above technologies. After reading through
> Logstash it seems the general use case is that there is a Logstash agent
> sitting on each machine that you want to aggregate logs from. This agent
> will then tail/read a list of logs and then you can send them off to
> RabbitMQ via their AMQP output. I see however there is also an AMQP input
> so instead of having an agent on each machine, why not just send the logs
> to AMQP and then have a Logstash read from that input? This would remove
> the need of having an agent on each machine. Are there performance reasons
> of why not to send everything via AMQP? If one would to do this in Rails
> (Unicorn server) would it be best to use Bunny or the async AMQP gem?
> >
> > Thanks
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-discuss at lists.rabbitmq.com
> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

-- 
NOTICE

This e-mail and any attachments are confidential and may contain copyright 
material of Brandscreen or third parties. If you are not the intended 
recipient of this email you should not read, print, re-transmit, store or 
act in reliance on this e-mail or any attachments, and should destroy all 
copies of them. Brandscreen does not guarantee the integrity of any emails 
or any attached files. The views or opinions expressed are the author's own 
and may not reflect the views or opinions of Brandscreen.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121031/d17bfc20/attachment.htm>