You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Stig Rohde Døssing (JIRA)" <ji...@apache.org> on 2019/04/01 17:10:02 UTC
[jira] [Commented] (STORM-3202) Include offset information to spout
metrics and remove storm-kafka-monitor
[ https://issues.apache.org/jira/browse/STORM-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806996#comment-16806996 ]
Stig Rohde Døssing commented on STORM-3202:
-------------------------------------------
[~kabhwan] Are you working on this? You are set as assignee.
> Include offset information to spout metrics and remove storm-kafka-monitor
> --------------------------------------------------------------------------
>
> Key: STORM-3202
> URL: https://issues.apache.org/jira/browse/STORM-3202
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Major
>
> To provide offset information on Kafka spout (old and new), we have storm-kafka-monitor module which is being run by UI (shell). This approach requires UI doing too many things - basically UI process does most of things via interacting with Nimbus - and also running external shell process in UI process per opening topology page doesn't look right.
> We could just let Spout include offset information into spout metric, and let UI leverage the information. I have been thinking about this approach but forgot about addressing it while thinking about generalizing the format. Now I think we don't have to put too much effort to generalize format, because Kafka spout is used mainly.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)