You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Prithvi Raj (JIRA)" <ji...@apache.org> on 2018/07/19 21:54:00 UTC
[jira] [Created] (FLINK-9898) Prometheus metrics reporter doesn't
respect `metrics.scope`
Prithvi Raj created FLINK-9898:
----------------------------------
Summary: 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: Metrics
Affects Versions: 1.5.1, 1.4.2, 1.4.1, 1.5.0, 1.4.0
Reporter: Prithvi Raj
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
(v7.6.3#76005)