You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by ni...@apache.org on 2016/04/28 00:10:52 UTC
samza git commit: SAMZA-937: fix document link to Coda Hale library
Repository: samza
Updated Branches:
refs/heads/master 7cd1d397b -> 84cf4ae0a
SAMZA-937: fix document link to Coda Hale library
Project: http://git-wip-us.apache.org/repos/asf/samza/repo
Commit: http://git-wip-us.apache.org/repos/asf/samza/commit/84cf4ae0
Tree: http://git-wip-us.apache.org/repos/asf/samza/tree/84cf4ae0
Diff: http://git-wip-us.apache.org/repos/asf/samza/diff/84cf4ae0
Branch: refs/heads/master
Commit: 84cf4ae0a217a91b5cd303c8b536cc4903671411
Parents: 7cd1d39
Author: Robin Tweedie <ro...@gmail.com>
Authored: Wed Apr 27 15:10:24 2016 -0700
Committer: Yi Pan (Data Infrastructure) <ni...@gmail.com>
Committed: Wed Apr 27 15:10:24 2016 -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/84cf4ae0/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 11a62f9..0423155 100644
--- a/docs/learn/documentation/versioned/container/metrics.md
+++ b/docs/learn/documentation/versioned/container/metrics.md
@@ -73,7 +73,7 @@ With this configuration, the job automatically sends several JSON-encoded messag
There is a separate message for each task instance, and the header tells you the job name, job ID and partition of the task. The metrics allow you to see how many messages have been processed and sent, the current offset in the input stream partition, and other details. There are additional messages which give you metrics about the JVM (heap size, garbage collection information, threads etc.), internal metrics of the Kafka producers and consumers, and more.
-It's easy to generate custom metrics in your job, if there's some value you want to keep an eye on. You can use Samza's built-in metrics framework, which is similar in design to Coda Hale's [metrics](http://metrics.codahale.com/) library.
+It's easy to generate custom metrics in your job, if there's some value you want to keep an eye on. You can use Samza's built-in metrics framework, which is similar in design to Coda Hale's [metrics](http://metrics.dropwizard.io/) library.
You can register your custom metrics through a [MetricsRegistry](../api/javadocs/org/apache/samza/metrics/MetricsRegistry.html). Your stream task needs to implement [InitableTask](../api/javadocs/org/apache/samza/task/InitableTask.html), so that you can get the metrics registry from the [TaskContext](../api/javadocs/org/apache/samza/task/TaskContext.html). This simple example shows how to count the number of messages processed by your task: