RabbitMQ Management Plugin

The rabbitmq-management plugin provides an HTTP-based API for management and monitoring of your RabbitMQ server, along with a browser-based UI and a command line tool, rabbitmqadmin.

Features include:

• Declare, list and delete exchanges, queues, bindings, users, virtual hosts and permissions.
• Monitor queue length, message rates globally and per channel, data rates per connection, etc.
• Send and receive messages.
• Monitor Erlang processes, file descriptors, memory use.
• Force close connections, purge queues.
• If you change configuration settings you must restart the Apache Service for the changes to take effect. First start the service and then start it again. Do not use the "Restart" option
• PrismMQ uses Erlang. In certain conditions, users have reported a "Failed to copy Erlang Cookie" or "Failed to find Erlang Cookie" message when a server is part of a domain. If you encounter this error message, try logging in as a local administrator (instead of using a network account) and run the installation again
• When all messages are processed, a new PrismMQ Complete flag (hidden field) is set to true, and the status changes from "Processing" to "Completed"

Launch RabbitMQ Management Plugin

1. In the browser address area, switch from "https" to "http". Clear the port information and anything after. Enter 15672 as the port. Press the Enter key.    
2. Enter the following login information and then tap or click the Login button. Username: prismguest   Password: prismguest  
    
3. Select the tab for the area you want to work with.  Below are sample line charts on the Overview tab showing queued messages and message rates.
      
4. When finished, click the Log out button.     

Refer to the following table for a description of the tabs on the RabbitMQ Console:

RabbitMQ Log Files
Prism uses RabbitMQ messaging service for data replication. RabbitMQ logs can provide valuable information for troubleshooting, especially issues related to replication.
RabbitMQ Log Management Best Practice for Prism
Change your RabbitMQ log level. Changing the log level will save hard drive space, reduce administration tasks and make it easier to search logs for errors. These log level settings are recommended by the Retail Pro Professional Services Team. You can find additional information about configuring RabbitMQ logs on the RabbitMQ website and on GitHub. The default log level in RabbitMQ is Info which is one severity below debug. When logging is set to the Info level, log entries will be recorded for events in the Info level and below, which includes Info, Warning, Error and Critical. This means that by default, only debug-level events are excluded from the logs. This is quite a lot of detail to include in the logs and is typically not necessary in a production environment. Instead, change the RabbitMQ log level to Error at each installation.
To edit the RabbitMQ log level:
Navigate to the C:\ProgramData\RetailPro\Server\RabbitMQ directory. Edit the file and change the contents to reflect the text in the log file below.
[{lager, [
                {handlers, [
                {lager_file_backend, [(file, "error.log"),
                {level, error},
                {date, "$00"},
                {size, 10485760},
                {count, 10}]}
]}]}]
 Refer to the following table for an explanation of the configuration file contents:

"$D0" (D-zero) Syntax
The $D0 syntax is taken from the syntax newsyslog uses in newsyslog.conf. The relevant extract follows.
Day, week, month and time format
The lead-in character for day, week and month specification is a '$' sign. The format of the day, week and month specification is: [Dhh], [Ww[Dhh]] and [Mdd[Dhh]], respectively. Hour specification is added on top of this, displayed as [Hmm]. Optional time fields default to midnight.

Examples