Argo Events AMQP Quick Fix - RabbitMQ Event Source

Argo Events AMQP event source consumes messages from RabbitMQ and other AMQP-compatible brokers. Misconfigured exchange or queue bindings cause message routing failures. This guide covers the fix.

Quick Fix

Wrong

amqp:
  example:
    url: amqp://guest:guest@localhost:5672/
    exchangeName: my-exchange
    exchangeType: fanout

The issue: missing queue binding declaration, no routingKey, and the exchangeType: fanout ignores routing keys. Messages go to the exchange but no queue consumes them.

Right

amqp:
  example:
    url: amqp://guest:guest@rabbitmq:5672/
    exchangeName: my-exchange
    exchangeType: topic
    routingKey: "events.*"
    queue: argo-events-queue
    exchangeDeclare:
      durable: true
      autoDelete: false

# Expected output after applying the fix
# AMQP connected to rabbitmq:5672
# Exchange my-exchange (topic, durable)
# Queue argo-events-queue bound with routing key events.*
# Messages routed to queue for consumption

Prevention

• Declare queue for message consumption
• Match exchangeType to routing behavior (topic, direct, fanout)
• Use appropriate routingKey pattern for topic exchanges
• Set exchangeDeclare properties matching broker configuration
• Test with RabbitMQ management UI to verify bindings

DodaTech Tools

Doda Browser's AMQP inspector shows exchange bindings and queue depths. DodaZIP archives AMQP configurations for disaster recovery. Durga Antivirus Pro validates AMQP TLS settings.

FAQ