Skip to main content

RabbitMQ

Connect a RabbitMQ broker so NudgeBee can inspect queues, exchanges and bindings, and act on them from workflows. RabbitMQ is listed under Messaging Queue in the integrations catalog.

info

RabbitMQ is connected through a Kubernetes Secret only. The broker must be reachable from a cluster where the NudgeBee agent is installed; there is no Proxy Agent mode for this integration.

When Do You Need This?​

This integration is optional. Connect RabbitMQ when you want to:

  • See queue depth, consumer counts and bindings while diagnosing a backlog or a stalled consumer.
  • Drive the broker from an automation using the mq.rabbitmqadmin.cli task — listing queues as evidence in a runbook, or publishing a probe message to verify a fix.

Prerequisites​

  • The management plugin enabled on the broker. rabbitmqadmin talks to the management HTTP API, not AMQP, so without it every command fails.

    rabbitmq-plugins enable rabbitmq_management

  • A RabbitMQ user NudgeBee can authenticate as, with the monitoring tag for read access. Grant management or administrator only if workflows need to publish or modify objects.

    rabbitmqctl add_user nudgebee '<YOUR_PASSWORD>'
    rabbitmqctl set_user_tags nudgebee monitoring
    rabbitmqctl set_permissions -p / nudgebee "" "" ".*"

Step 1: Create the Kubernetes Secret​

The secret must contain all four keys:

KeyValue
RABBITMQ_HOSTHostname or service DNS name, e.g. rabbitmq.messaging.svc.cluster.local
RABBITMQ_PORTPort NudgeBee connects on. The management API listens on 15672 by default.
RABBITMQ_USERUsername
RABBITMQ_PASSWORDPassword
kubectl create secret generic rabbit-secret \
  --namespace messaging \
  --from-literal=RABBITMQ_HOST=rabbitmq.messaging.svc.cluster.local \
  --from-literal=RABBITMQ_PORT=15672 \
  --from-literal=RABBITMQ_USER=nudgebee \
  --from-literal=RABBITMQ_PASSWORD='<YOUR_PASSWORD>'

Step 2: Configure the Integration in NudgeBee​

Navigate to Admin > Integrations > Messaging Queue and select RabbitMQ, then click Add Rabbitmq Account.

The RabbitMQ tile in the Messaging Queue tab of the integrations catalog

  • Name of RabbitMq * (Required) — How this broker is identified elsewhere in NudgeBee, e.g. orders-broker-prod.
  • Select Account * (Required) — The NudgeBee account this connection belongs to. Selecting several lets one broker serve multiple clusters.
  • Rabbitmq Secret in k8s * (Required) — The name of the secret created in Step 1.

The RabbitMQ configuration form, which takes a Kubernetes secret and offers no Proxy Agent mode

Step 3: Test and Save​

Click Test Connection, then Save.

Verify the Integration​

  1. Click Test Connection on the form — it should succeed before you save.
  2. In a workflow, run an mq.rabbitmqadmin.cli task with the command list queues. The response should list your queues with their message counts.

Troubleshooting​

SymptomLikely CauseFix
Every command fails to connectManagement plugin not enabledrabbitmq-plugins enable rabbitmq_management and retry.
Connection refused on port 5672AMQP port used instead of the management portSet RABBITMQ_PORT to the management API port, 15672 by default.
401 UnauthorizedWrong credentials, or the user has no management accessConfirm the password and set at least the monitoring user tag.
list queues returns nothingThe user has no permissions on the vhostrabbitmqctl set_permissions -p / nudgebee "" "" ".*"
Publish commands are refusedThe user only has read accessGrant write permissions on the vhost, or the management tag.
Secret saves but connection failsA key is missing or misspelledThe secret must contain all four keys exactly as listed above.