[
https://issues.apache.org/jira/browse/STORM-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272112#comment-15272112
]
ASF GitHub Bot commented on STORM-433:
--------------------------------------
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/236#issuecomment-217110521
I am preparing a patch for publishing in-backlog (receive-queue) and
out-backlog (send-queue). I can see the average value of these metrics on UI
over each time window period but only in executors section. (No aggregation
over component level etc) Also users may be interested in instant value of
these metrics and I don't know how will I fit that into UI. any suggestions are
welcome.
> Give users visibility to the depth of queues at each bolt
> ---------------------------------------------------------
>
> Key: STORM-433
> URL: https://issues.apache.org/jira/browse/STORM-433
> Project: Apache Storm
> Issue Type: Wish
> Components: storm-core
> Reporter: Dane Hammer
> Assignee: Kyle Nusbaum
> Priority: Minor
>
> I envision being able to browse the Storm UI and see where queues of tuples
> are backing up.
> Today if I see latencies increasing at a bolt, it may not be due to anything
> specific to that bolt, but that it is backed up behind an overwhelmed bolt
> (which has too low of parallelism or too high of latency).
> I would expect this could use sampling like the metrics reported to the UI
> today, and just retrieve data from netty about the state of the queues. I
> wouldn't imagine supporting zeromq on the first pass.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
