From 44e52acfc0067bbdfce65b6a0abc026a7af81055 Mon Sep 17 00:00:00 2001 From: Charles Allen Date: Wed, 4 May 2016 10:30:02 -0700 Subject: [PATCH] Link up metrics configuration to what they mean (#2921) --- docs/content/configuration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/configuration/index.md b/docs/content/configuration/index.md index f86ec183b86..fc560bcf33c 100644 --- a/docs/content/configuration/index.md +++ b/docs/content/configuration/index.md @@ -133,7 +133,7 @@ The following monitors are available: ### Emitting Metrics -The Druid servers emit various metrics and alerts via something we call an Emitter. There are three emitter implementations included with the code, a "noop" emitter, one that just logs to log4j ("logging", which is used by default if no emitter is specified) and one that does POSTs of JSON events to a server ("http"). The properties for using the logging emitter are described below. +The Druid servers [emit various metrics](../operations/metrics.html) and alerts via something we call an Emitter. There are three emitter implementations included with the code, a "noop" emitter, one that just logs to log4j ("logging", which is used by default if no emitter is specified) and one that does POSTs of JSON events to a server ("http"). The properties for using the logging emitter are described below. |Property|Description|Default| |--------|-----------|-------|