[ 
https://issues.apache.org/jira/browse/KAFKA-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388189#comment-16388189
 ] 

Guozhang Wang commented on KAFKA-5613:
--------------------------------------

That's a good question. I looked through 
https://github.com/apache/kafka/pull/3547 and one caveat is that it reports all 
metrics to the endpoint than allowing users to selectively pick which objects / 
attributes to report. So just to clarify my stands a bit more here:

1. For the performance testing and benchmarking purposes where users would more 
likely do manual work like starting processes, starting jmx tools, etc, I think 
the HTTPMetricsReporter may not be able to completely replace JMXTool's 
functionality. But maybe JMXTrans can completely replace JMXTools.

2. For non-performance testing system test itself, I agree that replacing 
jmx.py with http.py would be a good idea.

> Deprecate JmxTool?
> ------------------
>
>                 Key: KAFKA-5613
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5613
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.11.0.0
>            Reporter: Ewen Cheslack-Postava
>            Priority: Major
>
> According to git-blame, JmxTool has been around since October 2011. We use it 
> in system tests, but we are thinking it might be best to replace it: 
> https://issues.apache.org/jira/browse/KAFKA-5612
> When making modifications for system tests, we've had to take into account 
> compatibility because this tool is technically included in our distribution 
> and, perhaps unintentionally, a public utility.
> We know that "real" tools for JMX, like jmxtrans, are more commonly used, but 
> we don't know who might be using JmxTool simply because it ships with Kafka. 
> That said, it also isn't documented in the Kafka documentation, so you 
> probably have to dig around to find it.
> Hopefully we can deprecate this and eventually move it either to a jar that 
> is only used for system tests, or even better just remove it entirely. To do 
> any of this, we'd probably need to do at least a cursory survey of the 
> community to get a feel for usage level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to