[
https://issues.apache.org/jira/browse/KAFKA-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355319#comment-14355319
]
Gwen Shapira commented on KAFKA-1930:
-------------------------------------
1. Completely agree about the client library issue. Managing dependencies can
be very very painful.
2. I'm not sure I'm convinced about the server side though.
I can see a lot of work involved in replacing everything we currently have
(both in Kafka itself and in various integration points), but I don't see the
clear benefits. Is it just the windowed counter for quotas? Or for being
aligned with the clients?
We also need to consider maintenance work. Flume has its own metrics and
occasionally new components and new requirements show up, and I can't say I'm
happy with the extra work involved.
> Move server over to new metrics library
> ---------------------------------------
>
> Key: KAFKA-1930
> URL: https://issues.apache.org/jira/browse/KAFKA-1930
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jay Kreps
>
> We are using org.apache.kafka.common.metrics on the clients, but using Coda
> Hale metrics on the server. We should move the server over to the new metrics
> package as well. This will help to make all our metrics self-documenting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
