RockteMQ-AI commented on issue #2589:
URL:
https://github.com/apache/rocketmq-dashboard/issues/2589#issuecomment-5413232726
**Issue Evaluation**
Category: `enhancement` | Status: **Evaluated**
**Feasibility:** Feasible
**Scope:** `server/src/main/java/.../ops/alert/` (AlertService,
AlertRepository), `web/src/pages/ops/alerts.tsx`
**Compatibility:** Backward-compatible — the existing unpaginated endpoint
remains for export and current callers.
The assessment confirms the problem: `AlertService.listRules()` calls
`alertRepository.findAllRules()` which materializes the full inventory. The
frontend renders with `pagination={false}` and both `toggleRule` and
`bulkToggleRules` scan the complete list.
Adding a `GET /api/alert-rules/page` endpoint with server-side name search,
enabled-state filter, bounded pagination, and stable ordering (`name ASC, id
ASC`) is straightforward. The existing `items / total / page / size` contract
can be reused from other paginated endpoints in the project.
---
*Automated evaluation by github-manager-bot*
--
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]
