You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI visually looks pretty cool. But I think the Wonderland Dashboard could be designed to be more scalable. What happens when there are ten, twenty or even hundreds of queues, vhosts or exchanges.
I think it would be better to have an initial global or sum total perspective. I also liked the original dashboard information, which contained the "running nodes". So, I think it would be better if initially the user saw a globals dashboard, showing the cluster running nodes, the total memory used, total number of queues, total number of Vhosts, etc.
But, make each item such as queues or vhosts clickable. When the user clicks on Vhosts they would then see a list of Vhosts, with total memory and total messages for each. Each of the individual Vhosts would also be clickable.
The second click, opens the Vhost and shows a list of queues, with name, memory, messages, consumers, unacknowledged.
This could be implemented internally by having the following APIs:
The UI visually looks pretty cool. But I think the Wonderland Dashboard could be designed to be more scalable. What happens when there are ten, twenty or even hundreds of queues, vhosts or exchanges.
I think it would be better to have an initial global or sum total perspective. I also liked the original dashboard information, which contained the "running nodes". So, I think it would be better if initially the user saw a globals dashboard, showing the cluster running nodes, the total memory used, total number of queues, total number of Vhosts, etc.
But, make each item such as queues or vhosts clickable. When the user clicks on Vhosts they would then see a list of Vhosts, with total memory and total messages for each. Each of the individual Vhosts would also be clickable.
The second click, opens the Vhost and shows a list of queues, with name, memory, messages, consumers, unacknowledged.
This could be implemented internally by having the following APIs:
curl -i http://localhost:9999/dashboard/dashboard
curl -i http://localhost:9999/dashboard/dashboard/vhost/LOLcats
curl -i http://localhost:9999/dashboard/dashboard/vhost/LOLcats/cats_queue
What do you think?
The text was updated successfully, but these errors were encountered: