[
https://issues.apache.org/jira/browse/STORM-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272741#comment-15272741
]
ASF GitHub Bot commented on STORM-433:
--------------------------------------
Github user erikdw commented on the pull request:
https://github.com/apache/storm/pull/236#issuecomment-217228874
@abhishekagarwal87 : awesome news!
Any way you can post a screenshot of the UI you are currently proposing?
At least please do so with the PR when you send it. That could help others to
brainstorm how to put such values into the UI. Maybe you're instead asking for
suggestions on how to handle *obtaining* the instantaneous values?
> 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)
