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

Marton Greber reassigned KUDU-3692:
-----------------------------------

    Assignee: Marton Greber

> Add table attribution to tablet metrics in /metrics_prometheus
> --------------------------------------------------------------
>
>                 Key: KUDU-3692
>                 URL: https://issues.apache.org/jira/browse/KUDU-3692
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: metrics, Prometheus
>    Affects Versions: 1.18.0
>            Reporter: Marton Greber
>            Assignee: Marton Greber
>            Priority: Major
>
> In 1.18.0 the Prometheus exposition for tablet metrics (/metrics_prometheus) 
> does not include table attribution. Tablet IDs appear in metric names (e.g., 
> kudu_tablet_<tablet_id>_live_row_count), but there are no Prometheus labels 
> that allow joining a tablet to its table.
> In contrast, the JSON metrics (/metrics) expose attributes like table_id, 
> table_name, and human-readable partition info under the tablet entity.
> While implementing this fix one should look into how much more work it would 
> take to have "label parity" with the existing json metrics that are available.
> Supplementary:
> Root issue reported on Slack:
> "I get all the metrics per tablet. The tabletID is in the metric name 
> (example: kudu_tablet_d3ef3d70f47a47fc8073593c8587f58b_live_row_count).
> Unfortunately, I can't find the mappings from a table_name to the tabletID in 
> the metric name."



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to