[
https://issues.apache.org/jira/browse/KAFKA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582722#comment-14582722
]
Jun Rao commented on KAFKA-2238:
--------------------------------
[~auradkar], took a look at your patch. Currently, the Kafka metrics reporter
is instantiated in Kafka.scala before KafkaConfig is constructed. So, even if
you put those properties related to reporters to KafkaConfig, they won't be
used. We will have to move the instantiation of the reporters to KafkaServer
for this to work. However, since currently we only have a CSV reporter, I am
not sure if it's worth doing.
> KafkaMetricsConfig cannot be configured in broker (KafkaConfig)
> ---------------------------------------------------------------
>
> Key: KAFKA-2238
> URL: https://issues.apache.org/jira/browse/KAFKA-2238
> Project: Kafka
> Issue Type: Bug
> Reporter: Aditya Auradkar
> Assignee: Aditya Auradkar
> Attachments: KAFKA-2238.patch
>
>
> All metrics config values are not included in KafkaConfig and consequently
> cannot be configured into the brokers. This is because the
> KafkaMetricsReporter is passed a properties object generated by calling
> toProps on KafkaConfig
> KafkaMetricsReporter.startReporters(new
> VerifiableProperties(serverConfig.toProps))
> However, KafkaConfig never writes these values into the properties object and
> hence these aren't configurable. The defaults always apply
> Add the following metrics to KafkaConfig
> kafka.metrics.reporters, kafka.metrics.polling.interval.secs,
> kafka.csv.metrics.reporter.enabled, kafka.csv.metrics.dir
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
