[
https://issues.apache.org/jira/browse/KAFKA-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kotwasinski updated KAFKA-6830:
------------------------------------
Description:
Currently, we have only one fetch request-related metric for a topic.
As fetch requests are used by both client consumers and replicating brokers,
it is impossible to tell if the particular partition (with replication factor >
1) is being actively read from client by consumers.
Rationale for this improvement: as owner of kafka installation, but not the
owner of clients, I want to know which topics still have active (real)
consumers.
Patch attached.
was:
Currently, we have only one fetch request-related metric for a topic.
As fetch requests are used by both client consumers and replicating brokers, it
is impossible to tell if the particular partition (with replication factor > 1)
is being actively read from client by consumers.
Rationale for this improvement: as owner of kafka installation, but not the
owner of clients, I want to know which topics still have active (real)
consumers.
> Add new metrics for consumer/replication fetch requests
> -------------------------------------------------------
>
> Key: KAFKA-6830
> URL: https://issues.apache.org/jira/browse/KAFKA-6830
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Adam Kotwasinski
> Priority: Major
>
> Currently, we have only one fetch request-related metric for a topic.
> As fetch requests are used by both client consumers and replicating brokers,
> it is impossible to tell if the particular partition (with replication factor
> > 1) is being actively read from client by consumers.
> Rationale for this improvement: as owner of kafka installation, but not the
> owner of clients, I want to know which topics still have active (real)
> consumers.
> Patch attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
