<br><br><div class="gmail_quote">On Wed, Jun 29, 2011 at 6:29 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;">
<br><div class="im">
On 29/06/11 23:17, Gavin M. Roy wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We've looked at doing passive queue declares to get queue depths for<br>
alerting, reporting and auto-scaling of our consumers. Unfortunately<br>
passive queue declares appear to require configure access. I can see why<br>
queue.declare requires this but passive commands perhaps should have a<br>
different bit setting?<br>
</blockquote>
<br></div>
That will change in the next release - passive declare won't require any permissions. The code change for that is already on 'default'.</blockquote><div><br></div><div>Great :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Another one that seems a bit strange is in order to acknowledge message<br>
receipt (i.e. Basic.Ack) it appears that one has to have the write<br>
permission set for the given user+queue.<br>
</blockquote>
<br></div>
That can't be right. basic.ack requires no permissions whatsoever.</blockquote><div><br></div><div>Hmm ok, will take a look then, I could be thinking of something else then, it's been fuzzy sitting in the back of my head on my "to send an email about" list when I came across the passive declare bit today when locking that down.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In addition, we are currently doing all of our monitoring via the<br>
Management Plugin's API. Unfortunately to get any data, the user calling<br>
the API to list information requires administration access. I'd love to<br>
be able to let Nagios/Your_Monitoring_<u></u>Solution_Here poll the Rabbit node<br>
and get data without giving it access to change all of the configuration<br>
state and remove users.<br>
</blockquote>
<br></div>
Again, that should change in the next release. The code for it is going through qa atm.<br></blockquote><div> </div><div>Awesome, thanks! </div></div><br>