Using the RabbitMQ Management Dashboard

This topic describes how to use the RabbitMQ Management Dashboard, and applies to both the on-demand and pre-provisioned services.

RabbitMQ Management Dashboard

Admin User

To gain access to the management dashboard as the admin user, visit http://pivotal-rabbitmq.SYS-DOMAIN. To retrieve your system domain, navigate to your Pivotal Application Service (PAS) or Elastic Runtime tile and locate the System Domain field of the Domains section.

The username and password is the username and password you provided in the RabbitMQ configuration in OpsManager, which is also shown in the Credentials tab.


Application Developer

Users of Cloud Foundry who create instances via the Apps Manager or the cf CLI also get access to the Management UI. This is done using credentials that provide access only to their particular vhost.

The appropriate URL is accessible via the Manage button within the Apps Manager.

Console manage

Or it is also injected into the VCAP_SERVICES environment variable provided to apps running on Cloud Foundry. This can also be found via the CLI using cf env <your app name>.

Cli manage


A TCP Syslog endpoint can be configured in OpsManager. Logs are currently only forwarded for the RabbitMQ cluster.

RabbitMQ CLI

If you wish to run commands such as rabbitmqctl then you have two options:

SSH into one of the machines running the rabbitmq-server. IPs can be found from the Status tab and access credentials from the Credentials tab within the RabbitMQ component of the installer. From there you need to bring RabbitMQ and Erlang into your environment and from there you can use rabbitmqctl:

bash-4.1# export PATH=$PATH:/var/vcap/packages/rabbitmq-server/bin
bash-4.1# export PATH=$PATH:/var/vcap/packages/erlang/bin
bash-4.1# rabbitmqctl cluster_status
Cluster status of node rabbit@node0 ...

Alternatively, install RabbitMQ and Erlang on a machine of your choice. Be sure to match versions of both to the cluster: the Management UI shows both the version of RabbitMQ and Erlang.

Then set your ~/.erlang.cookie to match the cookie used in the cluster (you may have supplied this as part of the installation; see above).

You will need to set up your /etc/hosts file to match the RabbitMQ nodes.

Create a pull request or raise an issue on the source for this page in GitHub