Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update metrics monitors names in Configuration.md 

Updated the metric package names to reflect the new names in 0.7
This commit is contained in:
Maarten Rijke 2015-03-02 11:29:48 +01:00
parent c21086b6a8
commit 092acaea9d
1 changed files with 8 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/content/Configuration.md
View File

@ -65,21 +65,17 @@ Druid nodes periodically emit metrics and different metrics monitors can be incl
|Property|Description|Default| |Property|Description|Default|
|--------|-----------|-------| |--------|-----------|-------|
|`druid.monitoring.emissionPeriod`|How often metrics are emitted.|PT1m| |`druid.monitoring.emissionPeriod`|How often metrics are emitted.|PT1m|
|`druid.monitoring.monitors`|Sets list of Druid monitors used by a node. Each monitor is specified as `com.metamx.metrics.<monitor-name>` (see below for names and more information). For example, you can specify monitors for a Broker with `druid.monitoring.monitors=["com.metamx.metrics.SysMonitor","com.metamx.metrics.JvmMonitor"]`.|none (no monitors)| |`druid.monitoring.monitors`|Sets list of Druid monitors used by a node. See below for names and more information. For example, you can specify monitors for a Broker with `druid.monitoring.monitors=["com.metamx.metrics.SysMonitor","com.metamx.metrics.JvmMonitor"]`.|none (no monitors)|
The following monitors are available: The following monitors are available:
* CacheMonitor &ndash; Emits metrics (to logs) about the segment results cache |Name|Description|
for Historical and Broker nodes. Reports typical cache statistics include |----|-----------|
hits, misses, rates, and size (bytes and number of entries), as well as |`io.druid.client.cache.CacheMonitor`|Emits metrics (to logs) about the segment results cache for Historical and Broker nodes. Reports typical cache statistics include hits, misses, rates, and size (bytes and number of entries), as well as timeouts and and errors.|
timeouts and and errors. |`com.metamx.metrics.SysMonitor`|This uses the [SIGAR library](http://www.hyperic.com/products/sigar) to report on various system activities and statuses. Make sure to add the [sigar library jar](https://repository.jboss.org/nexus/content/repositories/thirdparty-uploads/org/hyperic/sigar/1.6.5.132/sigar-1.6.5.132.jar) to your classpath if using this monitor.|
* SysMonitor &ndash; This uses the [SIGAR library](http://www.hyperic.com/products/sigar) |`io.druid.server.metrics.ServerMonitor`|Reports statistics on Historical nodes.|
to report on various system activities and statuses. Make sure to add the |`com.metamx.metrics.JvmMonitor`|Reports JVM-related statistics.|
[sigar library jar](https://repository.jboss.org/nexus/content/repositories/thirdparty-uploads/org/hyperic/sigar/1.6.5.132/sigar-1.6.5.132.jar) |`io.druid.segment.realtime.RealtimeMetricsMonitor`|Reports statistics on Realtime nodes.|
to your classpath if using this monitor.
* ServerMonitor &ndash; Reports statistics on Historical nodes.
* JvmMonitor &ndash; Reports JVM-related statistics.
* RealtimeMetricsMonitor &ndash; Reports statistics on Realtime nodes.
### Emitting Metrics ### Emitting Metrics