[
https://issues.apache.org/jira/browse/KAFKA-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134056#comment-13134056
]
Chris Burroughs commented on KAFKA-166:
---------------------------------------
Coda Hale's metrics package has built in support for export:
https://github.com/codahale/metrics/commit/fce41d75046129a72e3582ae24ac698812d0fe53
Since we will inevitable want more than just average throughput (such as
percentiles for latency to judge jitter). We might want to consider switching
to that.
> Create a tool to jump JMX data to a csv file to help build out performance
> tests
> --------------------------------------------------------------------------------
>
> Key: KAFKA-166
> URL: https://issues.apache.org/jira/browse/KAFKA-166
> Project: Kafka
> Issue Type: New Feature
> Components: core
> Affects Versions: 0.8
> Reporter: Jay Kreps
> Assignee: Jay Kreps
> Attachments: KAFKA-166.patch
>
>
> In order to get sane performance stats we need to be able to integrate the
> values we keep in JMX. To enable this it would be nice to have a generic tool
> that dumped JMX stats to a csv file. We could use this against the producer,
> consumer, and broker to collect kafka metrics while the tests were running.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
