[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294238#comment-14294238
]
Joel Koshy commented on KAFKA-1902:
-----------------------------------
It's unfortunate it seems graphite does not allow overriding the separator for
hierarchy.
Jun, I'm not sure if Jason meant the following when he mentioned replacing the
dots with underscore - since he mentioned that it should be "navigable" (by
which I presume hierarchy). i.e., it would be more like:
topic.mytopic$with$dot.clientid.myclientId$with$dot - i.e., this way a graphite
user can browse the hierarchy as before (although the topic names are fudged).
It definitely loses information as you pointed out but that is probably okay
since the scope is really only relevant for the graphite reporter.
> fix MetricName so that Yammer reporter can work correctly
> ---------------------------------------------------------
>
> Key: KAFKA-1902
> URL: https://issues.apache.org/jira/browse/KAFKA-1902
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jun Rao
> Assignee: Jun Rao
> Priority: Blocker
> Fix For: 0.8.2
>
> Attachments: kafka-1902.patch
>
>
> Currently, we create MetricName in the following format.
> group: "kafka.server"
> type: "BrokerTopicMetrics"
> name: "BytesInPerSec"
> scope: null
> mBeanName:
> "kafka.server:type=BrokerTopicMetrics,name=BytesInPerSec,topic=test"
> However, Yammer metric reporter seems to only use the first four fields
> group, type, name and scope during reporting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
