[jira] [Closed] (FLINK-9898) Prometheus metrics reporter doesn't respect `metrics.scope`

["Till Rohrmann (Jira)" <ji...@apache.org>]

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

Till Rohrmann closed FLINK-9898.
--------------------------------
    Resolution: Duplicate

> Prometheus metrics reporter doesn't respect `metrics.scope`
> -----------------------------------------------------------
>
>                 Key: FLINK-9898
>                 URL: https://issues.apache.org/jira/browse/FLINK-9898
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Metrics
>    Affects Versions: 1.4.0, 1.4.1, 1.4.2, 1.5.0, 1.5.1
>            Reporter: Prithvi Raj
>            Priority: Major
>
> The Apache Flink [documentation|https://ci.apache.org/projects/flink/flink-docs-release-1.5/monitoring/metrics.html#system-scope] details that users may change the default scope of metrics emitted by using a scope format. 
> Changing the scope format allows end users to store metrics with lower cardinality while introducing the drawback of being unable to differentiate between metrics from different tasks/operators/etc sharing the same name. 
> With the Prometheus reporter, regardless of the scope format used, every variable is always emitted. 
> Would it be reasonable for the Prometheus reporter to respect the scope format and only emit dimensions that are in scope?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)