You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jiahong Li (JIRA)" <ji...@apache.org> on 2014/05/16 13:19:16 UTC
[jira] [Updated] (STORM-312) 'storm monitor' to monitor throughput
performance interactively
[ https://issues.apache.org/jira/browse/STORM-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiahong Li updated STORM-312:
-----------------------------
Description:
This cmd line tool 'storm monitor' will use Nimbus.Client to get throughput information from Nimbus Server.
1)One can specify topology's name, component's name to monitor it's throughput interactively.
2) It will statistics 'emit' and/or 'transferred' throughput in a given time window and print it in a given time frequency
The implementation will be much like yahoo's storm-perf-test (http://yahooeng.tumblr.com/post/64758709722/making-storm-fly-with-netty)
was:
This cmd line tool 'storm monitor' will use Nimbus.Client to get throughput information from Nimbus Server.
1)One can specify topology's name, component's name or type of component such as 'spouts'/'bolt', without knowing any components' name.
2) It will statistics 'emit' and/or 'transferred' throughput in a given time window and print it in a given time frequency
The implementation will be much like yahoo's storm-perf-test (http://yahooeng.tumblr.com/post/64758709722/making-storm-fly-with-netty) except for monitoring by component's type without knowning any components' name.
> 'storm monitor' to monitor throughput performance interactively
> ---------------------------------------------------------------
>
> Key: STORM-312
> URL: https://issues.apache.org/jira/browse/STORM-312
> Project: Apache Storm (Incubating)
> Issue Type: New Feature
> Reporter: Jiahong Li
> Labels: cmd-line-monitor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> This cmd line tool 'storm monitor' will use Nimbus.Client to get throughput information from Nimbus Server.
> 1)One can specify topology's name, component's name to monitor it's throughput interactively.
> 2) It will statistics 'emit' and/or 'transferred' throughput in a given time window and print it in a given time frequency
> The implementation will be much like yahoo's storm-perf-test (http://yahooeng.tumblr.com/post/64758709722/making-storm-fly-with-netty)
--
This message was sent by Atlassian JIRA
(v6.2#6252)