[jira] [Resolved] (KAFKA-541) Use metrics CSV reporter instead of jmx tool for system tests

["Neha Narkhede (JIRA)" <ji...@apache.org>]

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

Neha Narkhede resolved KAFKA-541.
---------------------------------

    Resolution: Fixed

Committed v4 after making the following changes to v3 -

1. Fixed a logging statement in metrics.py since the newly added statement threw a runtime error
2. Fixed KafkaProject.scala to point to the right metrics package version (3.0.1)
3. Fixed the ConsumerConfig constructor argument to be a val and removed the getter API added in v3
                
> Use metrics CSV reporter instead of jmx tool for system tests
> -------------------------------------------------------------
>
>                 Key: KAFKA-541
>                 URL: https://issues.apache.org/jira/browse/KAFKA-541
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Joel Koshy
>            Assignee: Yang Ye
>         Attachments: kafka_541_v1.diff, kafka_541_v2.diff, kafka_541_v3.diff, metrics-annotation-3.0.1.jar, metrics-core-3.0.1.jar
>
>
> The existing system test framework spawns off a bunch of jmxtool processes to collect metrics. This is rather heavy-weight and also, requires advance knowledge of all the beans (many of which are dynamically registered). E.g., per-topic stats pop-up only after the topics are produced to.
> Since we are using metrics-core, we can just turn on the CSV reporter to collect these stats. I had originally thought version 2.1.3 had various bugs that rendered it unusable for CSV reporter, but I gave it another try and it seems to be fine. Will post some output.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira