<div>
This would certainly be a possibility.
</div><div><br></div><div>I was thinking I might intercept the OTP error_logger during the Rabbit boot sequence and add a syslogd client as a report handler, so that I'm only injecting code into an existing execution as opposed to having to run an extra moving part. But I haven't looked into this in detail yet.</div>
<div></div>
<p style="color: #A0A0A8;">On Tuesday, 12 March 2013 at 14:47, Brett Cameron wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>
<p style="margin: 0px; "><span lang="EN-NZ">Could you write a little client that
leverages the amq.rabbitmq.log exchange? Log file entries are published to this
exchange, using the severity level of log messages as the routing key (severity
levels are “info”, “warning”, and “error”), so if you bind a queue or three to
this exchange you can have clients consume the log messages. A client could
then call syslog() to poke stuff into syslog, etc. </span></p>
<p style="margin: 0px; "><span lang="EN-NZ"> </span></p>
<p style="margin: 0px; "><span lang="EN-NZ">Although I suppose this still equates to
having to deploy another moving part, albeit a small one.</span></p>
<p style="margin: 0px; "><span lang="EN-NZ"> </span></p>
<br><br><div>On Tue, Mar 12, 2013 at 11:40 PM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com" target="_blank">0x6e6562@gmail.com</a>></span> wrote:<br><blockquote type="cite"><div>
<div>
<div><span style="color:rgb(160,160,168)">On Monday, 11 March 2013 at 23:14, Dave Lambley wrote:</span></div><blockquote type="cite"><div>
<span><div><div><div>On 11 March 2013 18:04, Ben Hood <<a href="mailto:0x6e6562@gmail.com" target="_blank">0x6e6562@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>I was wondering whether there is well defined way of forwarding all Rabbit</div>
<div>logs to syslog.</div></div></blockquote><div><br></div><div>We're using a bit of Perl to forward our messages into logstash and</div><div>eventually Kibana,</div><div><br></div><div><a href="http://search.cpan.org/dist/Message-Passing-Syslog/lib/Message/Passing/Syslog.pm" target="_blank">http://search.cpan.org/dist/Message-Passing-Syslog/lib/Message/Passing/Syslog.pm</a></div>
<div><a href="http://search.cpan.org/dist/Message-Passing-AMQP/lib/Message/Passing/AMQP.pm" target="_blank">http://search.cpan.org/dist/Message-Passing-AMQP/lib/Message/Passing/AMQP.pm</a></div><div><br></div><div>We tried the logstash agent, but found it too memory hungry to run on</div>
<div>all our hosts.</div></div></div></span></div></blockquote><div><br></div></div><div>Hi Jason and Dave,</div><div><br></div><div>Thanks for the pointers to log stash, imfile and message passing - they are certainly all good options. I guess there is currently no out of the box way to get Rabbit to send stuff directly to syslog without having to deploy a separate moving part.</div>
<div><br></div><div>Cheers,</div><div><br></div><div>Ben</div>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></div></blockquote></div><br>
</div><div><div>_______________________________________________</div><div>rabbitmq-discuss mailing list</div><div><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a></div><div><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>