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

Flink Jira Bot updated FLINK-17495:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-assigned  
(was: auto-deprioritized-major pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it. If the "warning_label" label is not removed in 7 days, the 
issue will be automatically unassigned.


> Add support for custom variables
> --------------------------------
>
>                 Key: FLINK-17495
>                 URL: https://issues.apache.org/jira/browse/FLINK-17495
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>            Reporter: jinhai
>            Assignee: Mason Chen
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, 
> stale-assigned
>
> Allow users to configure additional labels, presumably via a new config 
> option {{metrics.scope.variables.add.}}
> E.g.,
> {code:java}
> metrics.scope.variables.add: key1:value1;key2:value2 {code}
> Configured variables should be added to the variables map of the root metric 
> group; this may allow us in the future (once we have generalized scope 
> formats a bit) to include them there as well.
>  
> Original description:
> {quote}We need to add some custom labels on Prometheus, so we can query by 
> them.?? ??
> Now we can add jobName\groupingKey to PrometheusPushGatewayReporter in 
> version 1.10, but not in PrometheusReporter.
> Can we add AbstractPrometheusReporter#addDimension method to support this, so 
> they will be no differences except for the metrics exposing mechanism 
> pulling/pushing.
> {quote}



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

Reply via email to