[
https://issues.apache.org/jira/browse/KAFKA-17313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhijeet Kumar updated KAFKA-17313:
-----------------------------------
Description:
Currently, the metric object name for tiered storage quotas metrics is set to
{*}kafka.server:type=RemoteLogManager{*}, but it should instead be
{*}kafka.log.remote:type=RemoteLogManager{*}.
This is because of a limitation where when creating a SensorAccess, it needs
org.apache.kafka.common.metrics.Metrics, but with this the prefix becomes
kafka.server and cannot be changed. We instead need to use KafkaMetricsGroup
but there is no way to create SensorAccess with it.
was:
Currently, the metric object name for tiered storage quotas metrics is set to
`kafka.server:type=RemoteLogManager`, but it should instead be
`kafka.log.remote:type=RemoteLogManager`.
This is because of a limitation where when creating a SensorAccess, it needs
org.apache.kafka.common.metrics.Metrics, but with this the prefix becomes
kafka.server and cannot be changed. We instead need to use KafkaMetricsGroup
but there is no way to create SensorAccess with it.
> Fix object metric name for Tiered Storage quotas
> ------------------------------------------------
>
> Key: KAFKA-17313
> URL: https://issues.apache.org/jira/browse/KAFKA-17313
> Project: Kafka
> Issue Type: Task
> Reporter: Abhijeet Kumar
> Priority: Major
>
> Currently, the metric object name for tiered storage quotas metrics is set to
> {*}kafka.server:type=RemoteLogManager{*}, but it should instead be
> {*}kafka.log.remote:type=RemoteLogManager{*}.
> This is because of a limitation where when creating a SensorAccess, it needs
> org.apache.kafka.common.metrics.Metrics, but with this the prefix becomes
> kafka.server and cannot be changed. We instead need to use KafkaMetricsGroup
> but there is no way to create SensorAccess with it.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
