You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/05/29 20:51:02 UTC
[jira] [Commented] (STORM-69) UI Visualizations
[ https://issues.apache.org/jira/browse/STORM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012704#comment-14012704 ]
ASF GitHub Bot commented on STORM-69:
-------------------------------------
GitHub user knusbaum opened a pull request:
https://github.com/apache/incubator-storm/pull/127
STORM-69: Storm UI Visualizations for Topologies
Adds a directed-graph topology visualization to the topology page using storm's metrics and a javascript library called 'Arbor.js' released under the BSD license.
Features:
- Colors to represent spouts and bolts: spouts are blue, bolts are colored between green and red depending on their capacity consumption
- Width of lines between components represents the flow of tuples going between the components relative to the other visible streams.
- Stream selector: Select the streams you want to see.
- Tuple count, name, and latency labels on nodes and edges
![storm-visualizations](https://cloud.githubusercontent.com/assets/1819836/3121975/bf60b42a-e761-11e3-8c44-bf605362b5a1.png)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/knusbaum/incubator-storm knusbaum-ui-visualizations
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/127.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #127
----
commit b930e100a9f74e832fd9142d0c825d9f24d0af1d
Author: Kyle Nusbaum <kn...@yahoo-inc.com>
Date: 2014-05-28T22:54:09Z
Storm UI Visualizations for Topologies
----
> 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)