alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-3082 Doc fix

Browse Source
This commit is contained in:
Gunnar Morling 2021-05-18 10:18:20 +02:00 committed by GitHub
parent d96c3138d6
commit 22a38a99ee
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
documentation/modules/ROOT/pages/operations/monitoring.adoc
View File

@ -13,7 +13,7 @@
toc::[]
You can use the JMX metrics provided by link:https://zookeeper.apache.org/doc/r3.1.2/zookeeperJMX.html[Zookeeper] and link:http://docs.confluent.io/3.0.0/kafka/monitoring.html[Kafka] to monitor {prodname}.
You can use the JMX metrics provided by link:https://zookeeper.apache.org/doc/r3.1.2/zookeeperJMX.html[Apache Zookeeper], link:https://kafka.apache.org/documentation/#monitoring[Apache Kafka], and https://kafka.apache.org/documentation/#connect_monitoring[Kafka Connect] to monitor {prodname}.
To use these metrics, you must enable them when you start the Zookeeper, Kafka, and Kafka Connect services.
Enabling JMX involves setting the correct environment variables.
ifdef::community[]
@ -148,9 +148,9 @@ endif::product[]
ifdef::community[]
[id="enabling-jmx-docker"]
=== Enabling JMX in Docker
== Enabling JMX in Docker
If you are running Zookeeper, Kafka, and Kafka Connect in Docker containers,
If you are running Zookeeper, Kafka, and Kafka Connect in via the {prodname} container images,
enabling JMX requires several additional environment variables that are not typically needed when running on a local machine.
This is because the JVM requires the host name to which it will advertise itself to JMX clients.
Thus, {prodname}'s Docker images for Zookeeper, Kafka, and Kafka Connect use several environment variables to enable and configure JMX.