[
https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201138#comment-14201138
]
Jun Rao commented on KAFKA-1723:
--------------------------------
[~otis], let me explain that a bit more. Historically, we have been using
metrics-core to expose mbeans in both the client and the server. When we added
the new java producer, we decided to use a metrics package of our own
(org.apache.kafka.common.metrics) to simplify the jar dependency. The new java
producer exposes a bunch of new mbeans (completely different from the old
producer) using our own metrics. The naming of those mbean is in the
description of the jira and is not completely consistent with those created by
metrics-core (after kafka-1481 is fixed). This jira is intended to make mbean
names created by our own metrics consistent with what's in metrics-core.
Longer term, our thinking is to eventually use our own metrics for the server
side mbean too.
> make the metrics name in new producer more standard
> ---------------------------------------------------
>
> Key: KAFKA-1723
> URL: https://issues.apache.org/jira/browse/KAFKA-1723
> Project: Kafka
> Issue Type: Sub-task
> Components: clients
> Affects Versions: 0.8.2
> Reporter: Jun Rao
> Fix For: 0.8.3
>
>
> The jmx name in the new producer looks like the following:
> kafka.producer.myclientid:type=mytopic
> However, this can be ambiguous since we allow "." in client id and topic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
