[
https://issues.apache.org/jira/browse/STORM-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271573#comment-15271573
]
ASF GitHub Bot commented on STORM-433:
--------------------------------------
Github user erikdw commented on the pull request:
https://github.com/apache/storm/pull/236#issuecomment-217026345
@knusbaum : I see you closed this. Are you planning to open a new PR for
publishing these stats? It would be a big help to us, we often wonder at
various behaviors we witness from our users' topologies, and the only mechanism
we have right now for getting visibility into the queue depths seems to be
getting every topology owner to use a custom metrics consumer to publish the
metrics which we would then need to provide fancy aggregation on top of.
Having it in the Storm UI and also in the API stats would be very very helpful.
> 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)
