[
https://issues.apache.org/jira/browse/STORM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968688#comment-13968688
]
Klaus Schaefers commented on STORM-69:
--------------------------------------
Hi, I have creates some prototype and published the code on github. The
visualization is a little different. You just have boxed presenting the
different bolts and spouts. Also this boxes have little mine dash boards inside
so you can see some custom metrics. its more design as a monitoring solution
that runs on a big screen in you ops center. Nonetheless it might be a good
starting point.
you can find the code here:
https://github.com/v3080/streamui
And a demo at:
http://vommond.de/streamui/streamui.html#method=showToplogy&id=WordCount
The entire UI is written in JS and communicates via REST with a server to get
data about the topology and the metrics. As it is a prototype I can easily
change the json format. Let me know if you are interesting in using it.
> UI Visualizations
> -----------------
>
> Key: STORM-69
> URL: https://issues.apache.org/jira/browse/STORM-69
> Project: Apache Storm (Incubating)
> Issue Type: New Feature
> Reporter: James Xu
>
> https://github.com/nathanmarz/storm/issues/368
> I've worked with Storm for a while now, and I can say that having a quick
> visual on the makeup of your topologies is worth a lot. It's far easier to
> simply look at a graph, and see the connections between named nodes, than to
> browse through code. Invaluable when you're debugging a problem in production.
> Along these lines, I think it would be a real asset to have a handful of
> useful visualizations in the UI.
> One example would be circle packing, where the containing circles are
> topologies, and the inner circles are topology components. See
> http://mbostock.github.com/d3/talk/20111116/pack-hierarchy.html. The idea
> would be to write it flexibly, so that the size of each circle is given by a
> function over the topology and/or node. You could imagine representing such
> things as throughput, latency, (received - acked), (# of executors occupied),
> etc in this way. It would be a quick visual indicator of how your topologies
> are behaving.
> Another example would be if you wanted a quick visual depiction of a topology
> -- you might use a graph, or a force-directed graph:
> http://mbostock.github.com/d3/talk/20111116/force-collapsible.html
> Many more ideas here: https://github.com/mbostock/d3/wiki/Gallery
> If you guys think any of these would be a valuable addition, I'd love to take
> a crack at it.
> ----------
> nathanmarz: I would like to see a force-directed graph of each topology, with
> the size of the edges between nodes indicating the amount of throughput
> passing between them. Once we improve the metrics (notably issues #362 and
> #363) we can use color to indicate which components are likely bottlenecks in
> the topology.
> It would be really cool if clicking on a node shows more detailed information
> (like a visualization of the incoming and outgoing throughput to each
> individual task in that component).
> ----------
> gsilk: I'm on it.
> ----------
> chenxiaozhao: i can‘t wait to see the force-directed graph ,which can show
> the incoming and outgoing throughput to each individual task in that component
--
This message was sent by Atlassian JIRA
(v6.2#6252)
