[ https://issues.apache.org/jira/browse/STORM-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806722#comment-16806722 ]
Stig Rohde Døssing commented on STORM-433: ------------------------------------------ [~dagit] This seems like it should be reasonably easy to implement on master. Metrics v2 was merged, and the queues were simplified since 1.x. I don't think anyone is working on this currently, but feel free to pick it up. > 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: Abhishek Agarwal > Priority: Minor > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > 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 (v7.6.3#76005)