<br><br><div class="gmail_quote">On Sat, Jul 2, 2011 at 1:30 PM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@rabbitmq.com">matthew@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
So, 31 unique IP downloads within 24 hours - I guess people like the<br>
idea of being able to see what the topologies are within their brokers.<br></blockquote><div><br></div><div>Love it, looks good, will love to see how it develops.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
My plans are generally along the following lines:<br>
<br>
0. allow the selection of different vhosts.<br>
<br>
1. hovering over a queue or channel should link the queue to its<br>
consuming channels, and vice versa.<br>
<br>
2. hovering over any item should produce a tool-tip-style box with all<br>
the other essential stats and details about the item. So for exchanges,<br>
type, arguments; for queues, durable, auto-delete, exclusive, plus the<br>
other stats about the nature of their content; channels, similarly, the<br>
usual suspects.<br>
<br>
3. optionally display connections above channels. This is only really<br>
useful if you have multiple channels per connection.<br>
<br>
4. the entries in the "disabled" select boxes on the left should be<br>
alphabetically sorted.<br>
<br>
5. channels should be grouped by connection.<br>
<br>
6. it seems wrong to me somehow that disabling an entire class (say,<br>
queues) does not add the queues that were being displayed to the select<br>
box. It does suggest that those items have just vanished.<br>
<br>
7. The bindings, and other links that may be being displayed should be<br>
coloured by their relative activity. Much information about the health<br>
of the system can be conveyed very quickly this way.<br>
<br>
Any requests? I liked Alvaro's idea of being able to construct things<br>
through this, but it'll take me quite some time to get that far.<br></blockquote><div><br></div><div>Perhaps using the management plugin velocity rates you could use thicker lines or annotate lines with message velocities?</div>
<div><br></div><div>Also visualization of cluster mechanics would be cool, though I'm not quite sure how one would represent it yet other than having it as part of the tooltips for the queues and connections.</div><div>
<br></div><div>Also I think it would be interesting instead of showing hovering over the queue to see the channels to instead represent the consumer tag as an object and link the channel to the consumer tag and the queue to the consumer tag. It could get quite big but to show the topology of:</div>
<div><br></div><div>connection -> channel -> consumer_tag <- queue <- exchange</div><div><br></div><div>Would be interesting. It's too bad there's not as exact of a topology for publishers, with regard to visualization like this.</div>
<div><br></div><div>Great work and cool idea,</div><div><br></div><div>Gavin</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><div>Looking forward to see how this develops.</div>
</div><br>