Warren
Documentation

Warren, feature by feature.

How to run Warren, and what each part of it does, with screenshots of the real app. New here? Start with Getting started; every option is in the configuration reference.

Get started

  • Getting started

    Run Warren in a minute with a demo broker, then point it at your own RabbitMQ with Docker or Helm.

Look at dead letters

  • The overview

    Every broker on one page for whoever is on call - dead letters, firing alerts, room before publishers are blocked, growing and largest queues, and what Warren did today.

  • Queues and why messages died

    The queue list with dead-letter queues on top, and the queue page that groups dead letters by reason, queue, routing key or exception, with notes for the team.

  • Reading a message

    Payload as a tree, table or raw, why the message is here, its death history, headers and properties, sensitive values hidden, and two or more messages compared field by field.

  • Set-up checks and the dead-letter map

    Warren reads your broker's set-up and names what loses or endangers dead letters - queues without a dead-letter exchange, exchanges into nowhere, quorum DLQ limits, unwatched DLQs - and draws where dead letters go.

  • Failures across queues

    One list of what fails in a whole cluster - the same exception in several dead-letter queues is one row - and a replay of a failure in every queue at once.

Act on dead letters

  • Replay dead letters

    Send dead-lettered messages back to their original exchange and routing key, throttled, with death headers stripped and publisher confirms on every message.

  • Dry run for bulk actions

    Replays, discards and parks of "the first N" or "every match", and purges, are checked first; the confirm takes exactly the messages Warren froze.

  • Park, discard and purge

    Move poison messages out of the way into a parking queue, remove messages for good with a reason, or empty a queue in one step; every action in the audit log.

  • Export, import and publish

    Copy dead letters into an NDJSON file without taking them, publish a file of messages to a queue or exchange, or write one test message by hand.

Monitor

  • History and "when is it empty?"

    Every queue sampled around the clock - messages, ready, unacked and consumers over time, and a forecast of when a queue is empty at the current pace.

  • Alert rules

    Rules that watch dead-letter queues, work queues and broker nodes, start from templates and notify a channel once, with repeats and an all-clear.

  • Alert channels and quiet hours

    Send alerts to Slack, Microsoft Teams, PagerDuty, Opsgenie, e-mail or any JSON webhook, and keep a channel quiet at night.

  • Prometheus metrics

    Scrape Warren's view of RabbitMQ (dead letters, room before publishers are blocked, firing alerts, replays) into Prometheus and Grafana, with ready-made alerting rules.

Automate

  • Replay rules

    Retry transient failures automatically - a rule replays the dead letters of one queue on a schedule, only those that match it, with attempt limits, pacing and a stop when it keeps failing.

  • API tokens and MCP server

    Personal API tokens for scripts and CI, and an MCP server so AI agents like Claude Code or Cursor can look at dead letters, group them and dry-run a replay.

Team and compliance

  • Users, roles and single sign-on

    Viewers read, operators act, admins manage alerts and users; local accounts or sign-in through your identity provider with roles from a claim.

  • Four-eyes approval

    Replays, discards and purges that wait for a second operator before they run, with both names in the audit log.

  • Audit log

    Every replay, park, discard, purge, export and publish with who, when, from where to where and the outcome per message; searchable, exportable as CSV and forwardable to a SIEM.

Reference

  • Quorum queues and delivery limits

    What RabbitMQ 3.13 and 4.x count as a delivery on a quorum queue, why a dead letter can arrive with its budget half used, and how Warren protects and shows it.

  • Configuration reference

    Every environment variable Warren reads, with its default and what it does.

  • Editions

    What Community, Team and Pro include, how a licence is installed, and how brokers are counted.

  • Keyboard

    Everything in Warren is reachable without a mouse - the shortcuts that matter at 3 a.m.