Repository: storm Updated Branches: refs/heads/1.x-branch 38b346ee5 -> df9525914
spelling fixes Project: http://git-wip-us.apache.org/repos/asf/storm/repo Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/d0df5a6c Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/d0df5a6c Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/d0df5a6c Branch: refs/heads/1.x-branch Commit: d0df5a6ce0f649be326b83f7adbbcae0b6180b3c Parents: 9aac3e0 Author: Aaron Gresch <[email protected]> Authored: Wed Apr 11 11:25:03 2018 -0500 Committer: Aaron Gresch <[email protected]> Committed: Wed Apr 11 11:25:03 2018 -0500 ---------------------------------------------------------------------- docs/metrics_v2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/storm/blob/d0df5a6c/docs/metrics_v2.md ---------------------------------------------------------------------- diff --git a/docs/metrics_v2.md b/docs/metrics_v2.md index cf05491..761d3e6 100644 --- a/docs/metrics_v2.md +++ b/docs/metrics_v2.md @@ -28,7 +28,7 @@ API documentation: [Timer](http://metrics.dropwizard.io/4.0.0/apidocs/com/codaha [Histogram](http://metrics.dropwizard.io/4.0.0/apidocs/com/codahale/metrics/Histogram.html), [Meter](http://metrics.dropwizard.io/4.0.0/apidocs/com/codahale/metrics/Meter.html), [Counter](http://metrics.dropwizard.io/4.0.0/apidocs/com/codahale/metrics/Counter.html), -[Guage](http://metrics.dropwizard.io/4.0.0/apidocs/com/codahale/metrics/Gauge.html) +[Gauge](http://metrics.dropwizard.io/4.0.0/apidocs/com/codahale/metrics/Gauge.html) Each of these methods takes a `name` parameter that acts as an identifier. When metrics are registered, Storm will add additional information such as hostname, port, topology ID, etc. to form a unique metric @@ -69,7 +69,7 @@ public class TupleCountingBolt extends BaseRichBolt { ## Metric Reporter Configuration - For metrics to be useful they must be *reported*, in other words sent somewhere where they can be consumed and analyed. + For metrics to be useful they must be *reported*, in other words sent somewhere where they can be consumed and analyzed. That can be as simple as writing them to a log file, sending them to a time series database, or exposing them via JMX. As of Storm 1.2.0 the following metric reporters are supported
