From b69f89d9f82c2daa81f59dad1f90899e08bd69fd Mon Sep 17 00:00:00 2001 From: Gian Merlino Date: Fri, 23 Feb 2024 05:19:37 -0800 Subject: [PATCH] Clarify where to set druid.monitoring.monitors. (#15729) --- docs/configuration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/index.md b/docs/configuration/index.md index c1355f05c33..03a55b69103 100644 --- a/docs/configuration/index.md +++ b/docs/configuration/index.md @@ -378,7 +378,7 @@ You can configure Druid services to emit [metrics](../operations/metrics.md) reg |Property|Description|Default| |--------|-----------|-------| |`druid.monitoring.emissionPeriod`| Frequency that Druid emits metrics.|`PT1M`| -|[`druid.monitoring.monitors`](#metrics-monitors)|Sets list of Druid monitors used by a service.|none (no monitors)| +|[`druid.monitoring.monitors`](#metrics-monitors)|Sets list of Druid monitors used by a service.

Because individual monitors sometimes only work on specific process types, it is best to set this property for each process type individually in e.g. `historical/runtime.properties` rather than `_common/common.runtime.properties`.|none (no monitors)| |[`druid.emitter`](#metrics-emitters)|Setting this value initializes one of the emitter modules.|`noop` (metric emission disabled by default)| #### Metrics monitors