[jira] [Closed] (FLINK-21585) Add options to include/exclude metrics

["Chesnay Schepler (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-21585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-21585.
------------------------------------
    Resolution: Fixed

master:
9cc3771577327d1f5eb7e2a44cd2b550aa602418
54f11971ac64ead7f42185f9ac16956954ea5b37

> Add options to include/exclude metrics
> --------------------------------------
>
>                 Key: FLINK-21585
>                 URL: https://issues.apache.org/jira/browse/FLINK-21585
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>            Reporter: Ashish Khatkar
>            Assignee: Chesnay Schepler
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> I work on Stream Processing team at Yelp. We provide centralized streaming infrastructure for Flink applications within our company. We have many Flink applications running in their own clusters with multiple applications having multiple jobs. Different applications have different usage of Flink metrics and not all applications use all the metrics provided by Flink. I was wondering if Flink can provide a configurable key for ex: {{metrics.reporter.<name>.scope.metrics.excludes}} or {{metrics.scope.excludes}} which can take a list of metric names that can be excluded by Flink metrics library. This will help us to scrape only the relevant metrics at an applications level and not bloat up our metrics infrastructure with metrics that are never used. We would like to use this with Prometheus Exporter.
> We can solve this at our end by writing a custom metric reporter which can provide this functionality. I think community can benefit from such an option directly provided by Flink. What do you think?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)