You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2018/01/13 08:10:00 UTC

[jira] [Resolved] (FLINK-8324) Expose another offsets metrics by using new metric API to specify user defined variables

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

Tzu-Li (Gordon) Tai resolved FLINK-8324.
----------------------------------------
    Resolution: Fixed

> 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)