You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/03/24 14:40:00 UTC

[jira] [Updated] (FLINK-21585) Provide a configurable way to skip metrics

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

Chesnay Schepler updated FLINK-21585:
-------------------------------------
    Fix Version/s: 1.16.0

> Provide a configurable way to skip 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
>             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)