Aias00 opened a new issue, #2570: URL: https://github.com/apache/rocketmq-dashboard/issues/2570
## Problem The legacy Business Alerts API has two coupled contract gaps: - `POST /api/alert-rules/create` accepts a caller-provided ID. The repository treats an existing ID as an update, so a malformed or stale create request can overwrite an existing rule. - `GET /api/alert-rules` materializes every business rule and the web page performs all filtering in memory. ## Scope - reject non-null IDs on the create path and keep insert/update semantics distinct - add a bounded, server-side paged Business Alerts inventory with filters and stable ordering - retain a full read only for YAML export compatibility - migrate the Business Alerts page to the paged contract ## Dependency This work stacks on #2533 because that PR introduces the Business/Cluster alert domain split in the same service and repository layer. ## Verification Add focused controller, service/repository, and web-page regression tests for both create rejection and paged filtering. -- 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]
