[jira] [Commented] (STORM-2783) De-couple "Spout Lag" metrics on Storm UI from Kafka Spout and StormKafkaMonitor

["Jungtaek Lim (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214247#comment-16214247 ] 

Jungtaek Lim commented on STORM-2783:
-------------------------------------

+1 on this. If we could construct an interface on spout information and let it pushed to built-in metrics, it should be flexible and non-Kafka spouts could enjoy similar benefit.

> De-couple "Spout Lag" metrics on Storm UI from Kafka Spout and StormKafkaMonitor
> --------------------------------------------------------------------------------
>
>                 Key: STORM-2783
>                 URL: https://issues.apache.org/jira/browse/STORM-2783
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>    Affects Versions: 2.0.0, 1.1.1
>            Reporter: Stephen Powis
>
> As a developer of a spout, I'd love to be able to publish lag metrics to the storm UI.  After digging into the source code for how the UI interacts with storm-kafka-monitor to get these metrics, it appears to be strongly coupled.  I believe that the concept of "Spout Lag" extends beyond the scope of just consuming from Kafka. 
> I'd like to propose the idea of restructuring how these metrics are queried by StormUI to a way that allows developers of other spouts to be able to "plug into" the UI.  The easiest way that springs to mind is to provide an interface that allows developers to code against.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)