The Particular throughput tool can be installed locally and run against a production system to discover the throughput of each endpoint in a system over a period of time.
This article details how to collect endpoint and throughput data when the system uses the RabbitMQ transport. Refer to the throughput counter main page for information how to install/uninstall the tool or for other data collection options.
Running the tool
To collect data from RabbitMQ, the management plugin must be enabled on the RabbitMQ broker. The tool will also require a login that can access the management UI.
Execute the tool with the RabbitMQ management URL, as in this example where the RabbitMQ broker is running on localhost:
throughput-counter rabbitmq --apiUrl http://localhost:15672
The tool will prompt for the username and password to access the RabbitMQ management interface. After that, it will take its initial reading, then sleep for 24 hours before taking its final reading and generating a report.
|Required – The URL for the RabbitMQ management site.|
|Masks sensitive information in the generated report. See masking private data.|
|Sets the customer name. If not provided, the tool will prompt for the information.|
|Will not prompt for user input, so that the tool can be used from environments such as a continuous integration system.|
|Will not perform the check, for use in environments when outgoing network access creates alerts.|
What does the tool do
After performing an interactive login to the RabbitMQ Management API, the tool will:
/to get basic information about the system, ensure that the current version of RabbitMQ is compatible with the tool, and that the necessary plugins are installed to be able to get queue throughput details.
/to discover queue names and to get the message stats for each queue. If more than 500 queues are present, the additional pages of data will be requested as well.
- The queries to
/will be repeated every 5 minutes over the 24-hour tool runtime. This way, the tool can continue counting if a restart of a RabbitMQ server instance causes the message stats to reset.