[
https://issues.apache.org/jira/browse/KAFKA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469043#comment-13469043
]
Joel Koshy commented on KAFKA-541:
----------------------------------
Actually, now I remember. metrics 3.0.0 fixes this issue:
https://github.com/codahale/metrics/pull/225
It affects us because we have different scopes for similar metrics. e.g.,
NumDelayedRequests in both FetchRequestPurgatory and ProducerRequestPurgatory,
so they collide.
E.g., with metrics 2.1.3 we would just have NumDelayedRequests.csv but with
3.0.0 we would have
kafka.server.ProducerRequestPurgatory.NumDelayedRequests.csv and
kafka.server.FetchRequestPurgatory.NumDelayedRequests.csv
I'll file a separate jira to upgrade to 3.* as this one is for getting our
system test framework to consume the generated csv files.
> 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
>
> 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
