[rabbitmq-discuss] Management plugin preview release
simon at rabbitmq.com
Mon Sep 13 16:26:00 BST 2010
On 13/09/10 15:28, Dave Greggory wrote:
> Sending to list...
> If we can keep the Status plugin around until Management plugin comes out of
> beta, that should be good enough for us. I realize Status plugin is also beta,
> but we're comfortable with it for now (as opposed to not having any monitoring
> at all), but I'd hate to have to put another beta plugin out there on a
> production system.
That sounds fairly plausible.
>>> 5. Ability to isolate plugin failures from taking down RabbitMQ - (ie run the
>>> plugin on a single RAM node in a cluster that no apps connect to, but from
>>> node monitor the status of other nodes in the cluster)
>> At the moment the management plugin isn't very sensible in the context of
>> clustering, but that will get fixed.
> To be explicit, you're saying that you plan to have some way to have the
> Management plugin show the state of nodes in the cluster other than the one it's
> running on? I much rather prefer this approach because that way, we can have a
> node in the cluster that isn't really used for messaging, but solely to monitor
> other nodes in the cluster that do the actual work.
That's the plan. Note that it's currently far from what's actually
happening, but it seems like the right thing to do in a clustered
>>> 6. Configurable permissions to lock down what can be done through the plugin
>> The short-term plan is to add a superuser bit to define whether users can
>> manipulate non-AMQP objects (users / vhosts / permissions) at all. For AMQP
>> objects the>existing permission system is used. Would this be adequate?
> Yep taking away access from users/vhosts/permissions should suffice in terms of
Cool. This is now implemented in the default branch.
Staff Engineer, RabbitMQ
SpringSource, a division of VMware
More information about the rabbitmq-discuss