Hi HN - We run a consultancy focused on RabbitMQ and regularly review production clusters for configuration risks, performance issues, and upgrade blockers.

One pattern we kept seeing: a lot of teams suspect something might be wrong (or aren’t sure if they’re safe to upgrade), but hesitate to engage external help without first understanding their current state. So we built a small self-service tool that analyses the output of: rabbitmqctl report

You run the command locally, upload the generated text file, and receive a PDF highlighting potential configuration risks, deprecated features, and upgrade considerations.

Important details: No credentials or cluster access required No agents to install It does not include message contents The report is intentionally limited in scope It’s meant as a starting point, not a substitute for a full health check

We built this by formalising a subset of checks we typically look at during early-stage reviews. It’s not exhaustive, but it can help surface obvious issues before a version upgrade or architecture change.

Would genuinely welcome feedback from anyone running RabbitMQ in production, especially on:

false positives missed signals or other checks you think would be useful Link: https://seventhstate.io/rabbitmq-health-checks/

Happy to answer questions.