-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scalable UI #7
Labels
Comments
The internal API structure won't change (i.e. the curl examples), but I agree with you regarding the clickable interface on wonderland. |
I added a basic drilldown interface in wonderland. Lemme know what you think |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: