Absolutely! You can retrieve the 'Consumer utilisation' metric both through client-side workarounds and directly via RabbitMQ's Management API. Let's break this down clearly:

1. Using RabbitMQ Clients #

First, a quick heads-up: The core AMQP protocol doesn't expose the 'Consumer utilisation' value natively—this is a computed metric generated by RabbitMQ's Management Plugin. So native AMQP clients (like the official Java, Python, or .NET clients) won't have a direct method to pull it.

That said, you can still fetch this value from your client code by calling the Management API programmatically:

• Use your language's HTTP client library to send requests to the Management API endpoint (details below).
• Or use a dedicated Management API client library (like rabbitmq-management-client for Java) that wraps these HTTP calls into simple, reusable methods.

2. Requesting via the RabbitMQ Management API #

This is the most straightforward way to get the 'Consumer utilisation' value. Here's how to do it:

Prerequisites #

• Make sure the RabbitMQ Management Plugin is enabled (it's usually on by default; if not, run rabbitmq-plugins enable rabbitmq_management).
• Have a RabbitMQ user with permission to access the Management API (default local credentials are guest/guest, but use dedicated, limited-privilege users in production).

API Endpoint #

Send a GET request to:

http://{rabbitmq-host}:15672/api/queues/{vhost-url-encoded}/{queue-name}

• Replace {rabbitmq-host} with your server address (e.g., localhost).
• For the default vhost /, URL-encode it as %2F.
• Replace {queue-name} with your target queue's name.

Authentication #

Use Basic Authentication with your RabbitMQ username and password.

Example with curl #

curl -u guest:guest http://localhost:15672/api/queues/%2F/my-test-queue

Response Details #

The JSON response will include a consumer_utilisation field, a float between 0 and 1. For example:

{
  "name": "my-test-queue",
  "vhost": "/",
  // ... other queue metadata ...
  "consumer_utilisation": 0.75,
  // ... other metrics ...
}

This value represents the share of time consumers are actively processing messages (0.75 means 75% utilisation).

3. Responding to the Value #

Once you have the consumer_utilisation value, you can use it in your application logic however you need:

• Trigger alerts if utilisation spikes above a threshold (e.g., 0.9) or drops too low (e.g., 0.1).
• Dynamically scale consumer instances to match workload demand.
• Log the metric for long-term monitoring and debugging.

内容的提问来源于stack exchange，提问作者Arquillian