RabbitMQ supports a variety of plugins. This page documents the plugins that ship with RabbitMQ 3.4.2.
To enable plugins, use the rabbitmq-plugins tool:
rabbitmq-plugins enable plugin-name
And to disable plugins again, use:
rabbitmq-plugins disable plugin-name
You can see a list of which plugins are enabled with:
The rabbitmq-plugins comand will enable or disable plugins by updating the plugin configuration file. It will then contact the running server to tell it to start or stop plugins as needed. You can use the -n option to specify a different node, or use --offline to only change the file.
For more information on rabbitmq-plugins, consult the manual page.
In addition to the plugins bundled with the server, we also offer binary downloads of plugins which have been contributed by authors in the community. See the community plugins page for more detail on which plugins are available and how to install them.
|Authentication / authorisation plugin using an external LDAP server.|
|Authentication mechanism plugin using SASL EXTERNAL to authenticate using SSL client certificates.|
|Consistent hash exchange type.|
|Scalable messaging across WANs and administrative domains.|
|Shows federation status in the management API and UI. Only of use when using rabbitmq_federation in conjunction with rabbitmq_management. In a heterogenous cluster this should be installed on the same nodes as rabbitmq_management.|
|A management / monitoring API over HTTP, along with a browser-based UI.|
|When installing the management plugin on some of the nodes in a cluster, you must install rabbitmq_management_agent on all of the nodes in the cluster. You can install the full management plugin on as many of the nodes as you want.|
|An adapter implementing the MQTT 3.1 protocol.|
|A plug-in for RabbitMQ that shovels messages from a queue on one broker to an exchange on another broker.|
|Shows shovel status in the management API and UI. See the plugin README for this plugin. Only of use when using rabbitmq_shovel in conjunction with rabbitmq_management. In a heterogenous cluster this should be installed on the same nodes as rabbitmq_management.|
|A gateway for exposing AMQP functionality via the STOMP protocol.|
Currently, all plugins below are experimental. This means we make no claims about their fitness for purpose or stability, though they are in general under active development.
|Broker topology visualiser plugin which is itself a plugin to the management plugin. Adds a Visualiser tab to the management web interface, which then flexibly and interactively displays channels, queues and exchanges, and the links between them.|
|Adds message tracing to the management plugin. Logs messages from the firehose in a couple of formats.|
|A bridge exposing rabbitmq_stomp to web browsers using WebSockets, using the WebSockets emulation / compatibility layer SockJS.|
|Adds some basic examples to rabbitmq_web_stomp: a simple "echo" service and a basic canvas-based collaboration tool.|
|An implementation of the AMQP 1.0 protocol.|