Any specific reason to build this dashboard for redis broker #2
Comments
|
That’s odd. The Redis broker should be about as fast or faster than the RMQ broker.
Either way, the reason this dashboard doesn’t support RMQ is because it can’t. AMQP does not provide any reliable way to inspect the state and contents of a queue. To gain access to a message’s contents, you have to remove it from the queue.
If you absolutely need to use RMQ, then I would suggest using its management UI. You can also leverage the Prometheus support in Dramatiq for monitoring (via something like Grafana).
…Sent from my iPhone
On Jun 24, 2019, at 12:41 PM, Satheesh K ***@***.***> wrote:
Is there any specific reason to build this dashboard only for redis broker. Because I tried to switch to redis broker so that I will be able to use this dashboard. But it is slow(took more time) compared to RabbitMQ broker. Any pointers how we can extend this for RabbitMQ broker? I tried to find out why redis is slower than rabbitmq as a broker and found out this link
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Ok, Thank you. I will try to find out why redis is slower than rabbitmq in my case. Closing the issue. |
|
@Bogdanp Would it be possible to use the RabbitMQ management plugin (the same one that powers the management UI) to provide a Dramatiq dashboard? I believe that's what Celery Flower does. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there any specific reason to build this dashboard only for redis broker. Because I tried to switch to redis broker so that I will be able to use this dashboard. But it is slow(took more time) compared to RabbitMQ broker. Any pointers how we can extend this for RabbitMQ broker? I tried to find out why redis is slower than rabbitmq as a broker and found out this link
The text was updated successfully, but these errors were encountered: