Getting started
Redrive talks to RabbitMQ over two protocols: the management API for topology and stats, and AMQP for reading and writing messages. One connection entry configures both.
Add a connection
Redrive opens on the connections list. Create a connection and fill in the form:
| Field | What it's for |
|---|---|
| Display name | The name shown in Redrive's connection list. |
| Host | The broker's hostname or IP address. Both protocols connect to it. |
| AMQP port | The messaging port, 5672 by default. The TLS switch beside it is for amqps listeners, usually on 5671. |
| Management API | Scheme and port of the management plugin, http on 15672 by default. |
| Username and Password | One broker account, used for both the management API and AMQP. |
| Trust any certificate | Skips certificate checks on both protocols. For development brokers with self-signed certificates; leave it off anywhere else. |
Paste an amqp:// or amqps:// URI anywhere in the form and Redrive prefills the host, port, TLS setting, and credentials from it.
Redrive encrypts the broker password before storing it. Where the encryption key lives is covered in Security.
Saving does not test the connection. The connections list probes the management API and AMQP separately and shows a status chip for each, so a wrong port or a rejected password surfaces there.
Permissions
Every operation runs as the account you saved. Browsing goes through the management API, which requires a management tag (management, monitoring, policymaker, or administrator all qualify) and enforces the same configure, write, and read vhost permissions as AMQP.
| Operation | Protocol | The account needs |
|---|---|---|
| Browse queues, exchanges, and stats | Management API | A management tag; read-only permissions are enough |
| Peek | AMQP | read on the queue |
| Purge | AMQP | read on the queue |
| Discard | AMQP | read on the queue |
| Redrive | AMQP | read on the queue and write on the default exchange |
| Publish | AMQP | write on the exchange |
| Delete a queue | Management API | configure on the queue |
| Add or remove a binding | Management API | write on the queue and read on the exchange |
A monitoring-tagged, read-only account is enough to browse a MassTransit error-queue topology. Grant
writepermissions only on the vhosts you redrive from.
Find your way around
The overview shows what the broker is running: product and version, cluster name, node, and totals for connections, channels, exchanges, queues, and consumers. A queued-messages chart tracks the total, ready, and unacknowledged counts as Redrive polls. Under it, each virtual host is listed with its message count; select one to open its queues.
The queue list has a name filter and chips that narrow it to error queues, idle queues, or queues without consumers. Group by service folds each queue together with its _error and _skipped siblings, following the MassTransit endpoint naming convention. Each row carries a publish-rate sparkline.
Opening a queue shows three tabs: overview, messages, and bindings. Peek, on the messages tab, reads a batch of messages over AMQP and requeues them, so nothing is consumed.
Select a peeked message to inspect it. Redrive shows the parsed MassTransit envelope when it finds one, the raw body, the AMQP headers, and the fault details MassTransit recorded when the message failed.
Next
Continue to Redriving to move messages out of an error queue.