Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/302#issuecomment-61989690
The metrics system is very generic, and not that complex. Essentially it
sets up a timer that will periodically call getValueAndReset on an instance of
IMetric. These values can be anything and are sent to an instance of
IMetricsConsumer that is residing in a bolt. It is up to the IMetricsConsumer
to decide what to do with Object the the IMetric created.
I agree that having an API closer to codahale would be good, but that is a
much bigger change. I would like to see that in a separate JIRA/pull request.
The big difference between the two approaches is that the storm metrics
associate the value with an individual bolt or spout instance. codahale and
most other metrics systems I have seen, associate the metrics with an arbitrary
name. We would need a way to bridge that gap in a clean/efficient way. I
would also like to see a lot of metrics added into the daemon processes.
Nimbus, Supervisor, and DRPC all need good monitoring.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
