techdocsmith commented on a change in pull request #11481:
URL: https://github.com/apache/druid/pull/11481#discussion_r734891404
##########
File path: docs/configuration/index.md
##########
@@ -343,14 +343,17 @@ Coordinator and Overlord log changes to lookups, segment
load/drop rules, dynami
### Enabling Metrics
-Druid processes periodically emit metrics and different metrics monitors can
be included. Each process can overwrite the default list of monitors.
+You can configure Druid processes to emit [metrics](../operations/metrics.md)
regularly from a number of [monitors](#metrics-monitors) via
[emitters](#metrics-emitters).
|Property|Description|Default|
|--------|-----------|-------|
-|`druid.monitoring.emissionPeriod`|How often metrics are emitted.|PT1M|
-|`druid.monitoring.monitors`|Sets list of Druid monitors used by a process.
See below for names and more information. For example, you can specify monitors
for a Broker with
`druid.monitoring.monitors=["org.apache.druid.java.util.metrics.SysMonitor","org.apache.druid.java.util.metrics.JvmMonitor"]`.|none
(no monitors)|
+|`druid.monitoring.emissionPeriod`| Frequency that Druid emits metrics.|`PT1M`|
+|[`druid.monitoring.monitors`](#metrics-monitors)|Sets list of Druid monitors
used by a process.|none (no monitors)|
+|[`druid.emitter`](#metrics-emitters)|Setting this value will initialize one
of the emitter modules.|`noop`|
Review comment:
```suggestion
|[`druid.emitter`](#metrics-emitters)|Setting this value initializes one of
the emitter modules.|`noop`|
```
##########
File path: docs/configuration/index.md
##########
@@ -397,28 +408,27 @@ The Druid servers [emit various
metrics](../operations/metrics.md) and alerts vi
|`druid.emitter.http.minHttpTimeoutMillis`|If the speed of filling batches
imposes timeout smaller than that, not even trying to send batch to endpoint,
because it will likely fail, not being able to send the data that fast.
Configure this depending based on emitter/successfulSending/minTimeMs metric.
Reasonable values are 10ms..100ms.|0|
|`druid.emitter.http.recipientBaseUrl`|The base URL to emit messages to. Druid
will POST JSON to be consumed at the HTTP endpoint specified by this
property.|none, required config|
-#### Http Emitter Module TLS Overrides
+##### HTTP Emitter Module TLS Overrides
-When emitting events to a TLS-enabled receiver, the Http Emitter will by
default use an SSLContext obtained via the
-process described at [Druid's internal communication over
TLS](../operations/tls-support.md), i.e., the same
+When emitting events to a TLS-enabled receiver, the HTTP Emitter will by
default use an SSLContext obtained via the process described at [Druid's
internal communication over TLS](../operations/tls-support.md), i.e., the same
Review comment:
```suggestion
By default, when sending events to a TLS-enabled receiver, the HTTP Emitter
uses an SSLContext obtained from the process described at [Druid's internal
communication over TLS](../operations/tls-support.md), i.e., the same
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
