[
https://issues.apache.org/jira/browse/KAFKA-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320881#comment-15320881
]
ASF GitHub Bot commented on KAFKA-3711:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1479
> Allow configuration of MetricsReporter subclasses
> -------------------------------------------------
>
> Key: KAFKA-3711
> URL: https://issues.apache.org/jira/browse/KAFKA-3711
> Project: Kafka
> Issue Type: Improvement
> Components: clients, streams
> Reporter: Jeff Klukas
> Assignee: Guozhang Wang
> Priority: Minor
> Fix For: 0.10.1.0
>
>
> The current interface for attaching metrics reporters to clients allows only
> defining a list of class names, but provides no means for configuring those
> reporters.
> There is at least one existing project
> (https://github.com/apakulov/kafka-graphite) that solves this problem by
> passing additional properties into the client, which then get passed on to
> the reporter. This seems to work quite well, but it generates warnings like
> {{The configuration kafka.graphite.metrics.prefix = foo was supplied but
> isn't a known config.}}
> Should passing arbitrary additional parameters like this be officially
> supported as the way to configure metrics reporters? Should these warnings
> about unrecognized parameters be removed?
> Perhaps there should be some mechanism for registering additional
> configuration parameters for clients to expect?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
