[
https://issues.apache.org/jira/browse/STORM-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196242#comment-14196242
]
ASF GitHub Bot commented on STORM-533:
--------------------------------------
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/302#issuecomment-61658959
+1 for the ideas. We should have more metrics about the connection status.
From other side, current storm metric system code is too hard to read and
too hard to use.
Maybe we should use mature library like codahale to ease this process,
instead of maintaining our own metric facility.
> Add metrics collection for IConnection
> --------------------------------------
>
> Key: STORM-533
> URL: https://issues.apache.org/jira/browse/STORM-533
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> It would really be great to get some metrics from an IConnection that are
> then sent to the metrics consumer.
> We have seen issues in the past where a fire wall rule is mis-configured and
> one host is unable to talk to another host. If we had some metrics about how
> many reconnection attempts are being made by the client to a given host we
> could easily diagnose this.
> There are other metrics that would be nice to know too, like how many
> bytes/tuples are being sent between different hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
