Apache Kafka (Linux)
Enable JMX on the Kafka cluster
To enable JMX on the Kafka cluster, perform the following steps:
-
Add the following to the KAFKA_JMX_OPTS variable of the startup script being used. By default, this file is called kafka-run-class.sh.
-Dcom.sun.management.jmxremote.port=<MY_JMX_PORT> -Dcom.sun.management.jmxremote.rmi.port=<MY_JMX_PORT> -Djava.rmi.server.hostname=<MY_IP_ADDRESS>
Where:
My_JMX_Port is the JMX port of the Kafka host.
My_IP_ADDRESS is the IP address of the Kafka host.
2. Make sure that you have the latest version of the Agent. In the /etc/fm-agent/fm_agent.cfg file or the manifest file, make sure that the Kafka JMX information is filled in as follows:
[apache_kafka_jmx]
host = <MY_IP_ADDRESS>
port = <MY_JMX_PORT>
3. Rebuild the FortiMonitor Agent metadata.
We currently do not support authentication so we highly recommend only allowing JMX on a local IP (like 127.0.0.1 or localhost)
Control panel configuration
Apache Kafka monitoring is added to a server from the Monitoring configuration tab of the Instance Details page. If you do not see Kafka as a discovered resource, rebuild the FortiMonitor Agent metadata.
Available metrics
|
Metric |
Unit |
|---|---|
|
Heap Memory - Committed |
Bytes |
|
Heap Memory - Max |
Bytes |
|
Heap Memory - Used |
Bytes |
|
Queued messages |
Count |
|
Replica Manager Unreplicated Partitions |
Count |
|
Topic Bytes In/sec |
Bytes per second |
|
Topic Bytes Out/sec |
Bytes per second |
|
Topic Messages In/sec |
Bytes per second |
If you have any additional questions, please contact our support team.