[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294499#comment-14294499
]
Joel Koshy commented on KAFKA-1902:
-----------------------------------
Jun - to answer your earlier question. I took a look at the GangliaReporter in
metrics 2.x and it does seem that the ganglia reporter also uses the scope
field.
http://grepcode.com/file/repo1.maven.org/maven2/com.yammer.metrics/metrics-ganglia/2.0.0-BETA18/com/yammer/metrics/reporting/GangliaReporter.java#447
So it seems that ganglia users should also be affected by this issue that
Jason reported
> 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)
