We finally found the issue: a bug in our code was causing most traffic to go to that one broker. Sorry for the false alarm and thanks for the help troubleshooting!<div><br></div><div>--</div><div>Raphael.<br><br><div class="gmail_quote">
On Wed, Oct 26, 2011 at 11:19 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Raphael,<div class="im"><br>
<br>
On 27/10/11 05:18, Raphael Simon wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there a way to easily retrieve the average ingress rate across all<br>
queues for a broker? Maybe what's happening is a rogue client is spamming that<br>
specific server. I'd like to see the average ingress rate across all our<br>
brokers to validate that theory.<br>
</blockquote>
<br></div>
The avg queue ingress rate should be easy to calculate by extracting the rate information for all queues through the management API.<br>
<br>
Wouldn't it be better to look at inbound connection data rates for though, e.g. identify the connection with the highest inbound rate? Or perhaps look at per-channel message stats. You can get at all of these through the management API.<br>
<br>
Regards,<br><font color="#888888">
<br>
Matthias.<br>
</font></blockquote></div><br></div>