SAMZA-367: add Timer to the docs
Project: http://git-wip-us.apache.org/repos/asf/samza/repo Commit: http://git-wip-us.apache.org/repos/asf/samza/commit/d20ae5c7 Tree: http://git-wip-us.apache.org/repos/asf/samza/tree/d20ae5c7 Diff: http://git-wip-us.apache.org/repos/asf/samza/diff/d20ae5c7 Branch: refs/heads/samza-sql Commit: d20ae5c77170eee1951dc371b27ff14166aa2110 Parents: 44d07f6 Author: Yan Fang <[email protected]> Authored: Wed Mar 25 17:11:50 2015 -0700 Committer: Yan Fang <[email protected]> Committed: Wed Mar 25 17:11:50 2015 -0700 ---------------------------------------------------------------------- docs/learn/documentation/versioned/container/metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/samza/blob/d20ae5c7/docs/learn/documentation/versioned/container/metrics.md ---------------------------------------------------------------------- diff --git a/docs/learn/documentation/versioned/container/metrics.md b/docs/learn/documentation/versioned/container/metrics.md index 8ec7740..11a62f9 100644 --- a/docs/learn/documentation/versioned/container/metrics.md +++ b/docs/learn/documentation/versioned/container/metrics.md @@ -95,7 +95,7 @@ public class MyJavaStreamTask implements StreamTask, InitableTask { } {% endhighlight %} -Samza currently supports two kind of metrics: [counters](../api/javadocs/org/apache/samza/metrics/Counter.html) and [gauges](../api/javadocs/org/apache/samza/metrics/Gauge.html). Use a counter when you want to track how often something occurs, and a gauge when you want to report the level of something, such as the size of a buffer. Each task instance (for each input stream partition) gets its own set of metrics. +Samza currently supports three kinds of metrics: [counters](../api/javadocs/org/apache/samza/metrics/Counter.html), [gauges](../api/javadocs/org/apache/samza/metrics/Gauge.html) and [timer](../api/javadocs/org/apache/samza/metrics/Timer.html). Use a counter when you want to track how often something occurs, a gauge when you want to report the level of something, such as the size of a buffer, and a timer when you want to know how much time the block of code spends. Each task instance (for each input stream partition) gets its own set of metrics. If you want to report metrics in some other way, e.g. directly to a graphing system (without going via Kafka), you can implement a [MetricsReporterFactory](../api/javadocs/org/apache/samza/metrics/MetricsReporterFactory.html) and reference it in your job configuration.
