[
https://issues.apache.org/jira/browse/FLINK-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319834#comment-16319834
]
ASF GitHub Bot commented on FLINK-8324:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/5214
Good idea. I think we should also update the metrics doc to educate this
addition.
> Expose another offsets metrics by using new metric API to specify user
> defined variables
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-8324
> URL: https://issues.apache.org/jira/browse/FLINK-8324
> Project: Flink
> Issue Type: Improvement
> Components: Kafka Connector
> Reporter: Wei-Che Wei
> Assignee: Wei-Che Wei
> Priority: Trivial
> Fix For: 1.5.0
>
>
> The {{current-offsets}} and {{committed-offsets}} metrics are now attached
> with topic name and partition id in the metric identity.
> It is not convenient to use these metrics in Prometheus, because user usually
> uses the same metric group name to group by those metrics which have the same
> meaning and uses tags to get the individual metric.
> For example, I will prefer to access {{current-offsets}} metric group and use
> {{partition-x}} tag to get the offset of partition x, instead of getting
> metric directly from {{current-offsets-partition-x}} metric.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
