[
https://issues.apache.org/jira/browse/KAFKA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Ye updated KAFKA-541:
--------------------------
Attachment: kafka_541_v2.diff
Changes since first patch:
1. make the kafka csv metrics reporter a singleton --- only one instance in one
JVM
2. adding csv metrics reporter support for producer / consumer
/producer-performance / console-consumer
3. fix a few places in the system test to make it actually working --- with
producer_performance and console-consumer, and plotting graph correctly
4. there's only one problem left : some of the metrics are of type "time",
according to the doc, timer reports data as both a Meter and Histagram. (this
is also verified in the JMX console)
But for the exported CSV file, we only see the header like:
# time,min,max,mean,median,stddev,95%,99%,99.9%
That's to say, we cannot find the Meter / rate related metrics.
For a fiew graphs requiring "One minute rate" from a timer metric (and only for
them), the data are not reported and graphs are not plotted
> 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
>
>
> 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
