Sweet, I suspected it but I thought I might ask anyway. Consequently, I've implemented a deny list feature for my reporter (based on groupNameKey and metricName). The reporter will skip reporting metrics if a metric's variables set contains keys that map to the groupNameKey and if the metric has a name equal to the specified metricName.
Configurations are specified as follows `groupNameKey1:metricName1;groupNameKey2:metricName2`. Thus, I can deny list KafkaConsumer (group name key) and committed_offsets (metric name) which correspond to the legacy kafka metrics. Would Flink appreciate this as a contribution? I can see this being used generically over all reporters. Best, Mason On Mon, Aug 23, 2021 at 8:21 AM Arvid Heise <ar...@apache.org> wrote: > Hi Mason, > > I'm afraid it's an all-or-nothing. Either you get the proxied metrics with > all partitions or none. > > You could also implement a custom MetricReporter that delegates to your > actual reporter and filters the respective metrics. > > Best, > > Arvid > > On Fri, Aug 20, 2021 at 8:16 AM Mason Chen <mas.chen6...@gmail.com> wrote: > >> FYI, I'm referring to the legacy offsets metric gauges. >> >> On Thu, Aug 19, 2021 at 4:53 PM Mason Chen <mas.chen6...@gmail.com> >> wrote: >> >>> Hi all, >>> >>> We have found that the per partition Kafka metrics contributes to a lot >>> of metrics being indexed by our metrics system. >>> >>> We would still like to have the proxied kafka metrics from the kafka >>> clients library. Is there a flag to only exclude Flink's additional Kafka >>> metrics? >>> >>> Best, >>> Mason >>> >>>
