Validate RabbitMQ on Google Cloud

Validate your RabbitMQ installation on the Google Cloud SUSE Linux Arm64 virtual machine. This baseline confirms:

• RabbitMQ service health
• Management plugin availability
• Queue operations (create, publish, consume)
• CLI tooling functionality (rabbitmqctl and rabbitmqadmin)

Check RabbitMQ node status

Verify that the RabbitMQ node is operational and healthy.

    

        
        
sudo rabbitmqctl status

    

• Node status reports RabbitMQ is running
• No active alarms
• Listeners are active on ports 5672 and 15672
• Memory and disk space are within safe limits

Verify enabled plugins

Confirm that the RabbitMQ management plugins are enabled.

    

        
        
sudo rabbitmq-plugins list | grep management

    

You should see an output similar to:

    

        
        [  ] rabbitmq_federation_management          4.2.0
[E*] rabbitmq_management                     4.2.0
[e*] rabbitmq_management_agent               4.2.0
[  ] rabbitmq_shovel_management              4.2.0
[  ] rabbitmq_stream_management              4.2.0

        
    

Validate RabbitMQ listeners

Ensure RabbitMQ is listening on the required ports.

    

        
        
sudo rabbitmqctl status | grep -A5 Listeners

    

You should see an output similar to:

    

        
        Listeners

Interface: [::], port: 15672, protocol: http, purpose: HTTP API
Interface: [::], port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication
Interface: [::], port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0

        
    

Download RabbitMQ Admin CLI tool

Download the rabbitmqadmin CLI tool from the local management endpoint.

    

        
        
curl -u guest:guest http://localhost:15672/cli/rabbitmqadmin -o rabbitmqadmin

    

Make the tool executable:

    

        
        
chmod +x rabbitmqadmin

    

Validate queue creation

Create a test queue to validate write operations.

    

        
        
./rabbitmqadmin declare queue name=testqueue durable=false

    

You should see an output similar to:

    

        
        queue declared

        
    

Publish a test message

Send a test message to the queue.

    

        
        
./rabbitmqadmin publish exchange=amq.default routing_key=testqueue payload="hello world"

    

You should see an output similar to:

    

        
        Message published

        
    

Consume message from queue

Retrieve messages from the queue to verify read functionality.

    

        
        
./rabbitmqadmin get queue=testqueue

    

You should see an output similar to:

    

        
        +-------------+----------+---------------+-------------+---------------+------------------+------------+-------------+
| routing_key | exchange | message_count |   payload   | payload_bytes | payload_encoding | properties | redelivered |
+-------------+----------+---------------+-------------+---------------+------------------+------------+-------------+
| testqueue   |          | 0             | hello world | 11            | string           |            | False       |
+-------------+----------+---------------+-------------+---------------+------------------+------------+-------------+

        
    

Verify queue state

Confirm that the queue is empty after consumption.

    

        
        
./rabbitmqadmin list queues name messages

    

You should see an output similar to:

    

        
        +--------------+----------+
|     name     | messages |
+--------------+----------+
| jobs         | 0        |
| order.events | 1        |
| testqueue    | 1        |

        
    

Baseline validation summary

• RabbitMQ node is running and healthy
• The management plugin is enabled and accessible
• Queue creation is successful
• Message publishing works as expected
• Message consumption functions correctly
• CLI tools operate without error

This confirms a successful baseline validation of RabbitMQ on a GCP SUSE Arm64 virtual machine.