Skip to content

[feat] paginate the monitoring metrics data table - #4309

Open
orangeCatDeveloper wants to merge 1 commit into
apache:masterfrom
orangeCatDeveloper:feat/1594-metrics-table-pagination
Open

[feat] paginate the monitoring metrics data table#4309
orangeCatDeveloper wants to merge 1 commit into
apache:masterfrom
orangeCatDeveloper:feat/1594-metrics-table-pagination

Conversation

@orangeCatDeveloper

@orangeCatDeveloper orangeCatDeveloper commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

What's changed?

Fixes #1594: a metric group with hundreds of rows renders as one unbounded scroll blob in the monitor detail card. The maintainer asked to "support pageable in monitoring metrics data table ui".

  • add front pagination to the row table: pager above 10 rows, size changer 10/20/50/100
  • page index resets on data reload and page size change; the scroll area shrinks while the pager is shown so the fixed-height card does not clip it
  • valueRows initialized to [] (the new template expression evaluates before the async load); single-row table and fullscreen modal reuse the same template and keep working

Before (200 rows, scroll only):
1594-before-no-pager
After (paged):
1594-after-pager
50/page (page index resets):
1594-pagesize50

Checklist

  • I have read the Contributing Guide
  • I have written the necessary doc or comment.
  • I have added the necessary unit tests and all cases have passed.

Add or update API

  • I have added the necessary e2e tests and all cases have passed.

A metric group with hundreds of rows rendered as one scroll blob in
the detail card (apache#1594). Add front pagination with a size changer;
page index resets on reload and page size change, and the scroll
budget shrinks when the pager is visible so it is not clipped by the
fixed-height card.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] <title>There is no paging condition in the interface. There are 200 statuses in it, but only 10 statuses are displayed.

1 participant