[
https://issues.apache.org/jira/browse/KAFKA-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012180#comment-18012180
]
Mickael Maison commented on KAFKA-15601:
----------------------------------------
I've been trying to implement a ClientTelemetryReceiver plugin but one issue I
ran into is the TTL of metrics. When exportMetrics() is called you don't know
which subscription rules matched so you have no idea of the push interval.
Either you keep metrics forever and end up exposing stale metrics from clients
that have disconnected, or you have to actively clear them all regularly as you
don't know how long they are valid for.
I wonder if we could provide the push interval as part of the provided context
so reporters can easily track and delete stale metrics. Is this something that
was considered?
> Client metrics and observability
> --------------------------------
>
> Key: KAFKA-15601
> URL: https://issues.apache.org/jira/browse/KAFKA-15601
> Project: Kafka
> Issue Type: Improvement
> Components: admin, clients, consumer, core, producer , streams
> Reporter: Apoorv Mittal
> Assignee: Apoorv Mittal
> Priority: Major
> Labels: kip
>
> This Jira tracks the development of KIP-714:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-714%3A+Client+metrics+and+observability]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
