[
https://issues.apache.org/jira/browse/KAFKA-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885900#comment-17885900
]
Chia-Ping Tsai commented on KAFKA-14893:
----------------------------------------
{quote}
KafkaMetricsReporter which is not part of the public API. It is solely used by
brokers. This requires using the Yammer API.
{quote}
I assumed `KafkaMetricsReporter` is a public API, since it can be configured by
`kafka.metrics.reporters`.
{quote}
it exports many broker metrics that are critical to monitor. We discussed
migrating from Yammer to our own metrics library (KafkaMetric) in the past but
there was compatibility issues.
{quote}
thanks for this input. I will check the discussion.
> Public API for reporting Yammer metrics
> ---------------------------------------
>
> Key: KAFKA-14893
> URL: https://issues.apache.org/jira/browse/KAFKA-14893
> Project: Kafka
> Issue Type: Improvement
> Components: core, metrics
> Reporter: Mickael Maison
> Assignee: Mickael Maison
> Priority: Major
>
> Server side metrics registered via the Yammer library are currently exposed
> via the KafkaMetricsReporter interface. This is configured by setting
> kafka.metrics.reporters in the server configuration.
> However the interface is defined in Scala in the core module so it is not
> part of the public API. This API also assumes implementations can access
> KafkaYammerMetrics.defaultRegistry(), which is also not part of the public
> API, in order to report metrics.
> Also this API should support reconfigurable configurations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
