RockteMQ-AI commented on issue #2277: URL: https://github.com/apache/rocketmq-dashboard/issues/2277#issuecomment-5308351577
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** Dashboard Studio — system-alert API (`GET /api/system-alerts`) and corresponding UI table **Compatibility:** Non-breaking if pagination defaults to returning all results when no page params are supplied Well-scoped performance improvement. The current design loads the full alert inventory on every request and filters client-side — this does not scale with alert history growth. **Suggested approach:** 1. Add `page`/`pageSize` query parameters (with sensible defaults, e.g. pageSize=20) and optional `level` filter to the backend endpoint. 2. Return results wrapped in the existing `PageResult` contract so the UI table can reuse the shared pagination component. 3. Ensure acknowledgement/clear mutations still operate on the canonical alert ID, not the page-relative index, so pagination does not break existing UX flows. Dependencies on #2271 / #2272 are noted — this change should remain orthogonal to point-lookup optimisations. --- *Automated evaluation by RockteMQ-AI* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
