You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "maohong (JIRA)" <ji...@apache.org> on 2019/08/02 07:16:00 UTC

[jira] [Updated] (KAFKA-8741) We should optimize the use of mx4j web interface

     [ https://issues.apache.org/jira/browse/KAFKA-8741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

maohong updated KAFKA-8741:
---------------------------
    Summary: We should optimize the use of mx4j web interface  (was: We should optimize the use of JMX web interface)

> We should optimize the use of mx4j web interface
> ------------------------------------------------
>
>                 Key: KAFKA-8741
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8741
>             Project: Kafka
>          Issue Type: Wish
>          Components: core
>    Affects Versions: 2.4.0
>            Reporter: maohong
>            Priority: Minor
>              Labels: mx4j-tools
>
> # Since mx4j-tools.jar is not packaged into the final released tgz file by default, we can't monitor kafka brokers by web inferface. If we want to do it, we must find a mx4j-tools.jar in the maven repository by our own and put it under the directory $KAFKA_HOME/libs, which is very inconvenient.
>  # In Mx4jLoader, we read the property values of 'kafka_mx4jenable' and 'mx4jport' from system properties, but there is no way for us to set the switch and customize the port of mx4j-tools. We could add a configuration item in kafka-run-class.sh. For example, if MX4J_PORT is set, we add -Dkafka_mx4jenable=true -Dmx4jport=$MX4J_PORT into the start command.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)