Aias00 opened a new issue, #2271: URL: https://github.com/apache/rocketmq-dashboard/issues/2271
## Problem Acknowledging one system alert first loads every alert and scans the result in memory. Toggling one alert rule and bulk toggling selected rules likewise load every rule before locating the requested IDs. These mutations become unnecessarily expensive as alert retention and rule inventories grow, even though the requested identifiers are already known. ## Expected behavior - Acknowledging an alert performs a point lookup by ID. - Single rule toggles use a point lookup. - Bulk rule toggles load only the submitted IDs. - Existing not-found and concurrent-deletion semantics remain unchanged. ## Scope Track 1 alert persistence. List-endpoint pagination is intentionally separate because it requires a REST/UI response-contract change. ## Acceptance criteria - Repository contracts expose point and selected-ID lookups. - No mutation path calls `findAlerts(null)` or `findAllRules()` to locate a known ID. - Focused service/repository tests cover successful, missing, and concurrent-delete outcomes. -- 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]
