RabbitGUI

I built RabbitGUI because working with RabbitMQ often meant jumping between the management UI, CLI tools, scripts, and a lot of manual message handling. The biggest pain point was debugging real-world message flows, especially dead-letter queues. I wanted a tool where I could safely inspect messages, understand how they got there, edit and replay them, and quickly see what was happening across different environments. RabbitGUI is my attempt to make that workflow much faster and more pleasant for developers. It’s still evolving, and I’d love to hear from people who work with RabbitMQ: what’s the most painful part of debugging or managing your queues today?

Managing dead-letter queues and trying to safely inspect live traffic without consuming messages has always been a headache with the default management UI.

Peeking at live queue traffic without consuming messages is the feature I've always wanted from the default management UI. The backlog drain-time forecast is a nice touch for on-call debugging. Does republishing from the dead-letter queue keep the original headers and routing key?

Inspecting live queue traffic without consuming messages, alongside editing and replaying dead-letter messages with throttling, targets the exact pain of the default RabbitMQ management UI. If you ever want AI help in the business, PZERO is at pzero.studio.