RockteMQ-AI commented on issue #2748: URL: https://github.com/apache/rocketmq-dashboard/issues/2748#issuecomment-5461470533
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** `server/src/main/java/org/apache/rocketmq/studio/ops/alert/`, persistence layer, `schema.sql` **Assessment:** The referenced files (`NotificationOutboxService.java`, `RmqAlertNotificationOutboxMapper.java`) and table (`rmq_alert_notification_outbox`) do not currently exist in the codebase. This appears to be a proposal for a new notification delivery retention mechanism rather than a defect in existing code. The current `rmq_alert_rule` and `rmq_system_alert` tables (schema.sql:244-265) handle alert rules and system alerts, but there is no dedicated delivery outbox with retention cleanup. This is a valid enhancement request. Implementation would require: 1. A new `rmq_alert_notification_outbox` table in `schema.sql` 2. A `NotificationOutboxService` with scheduled cleanup of terminal (`DELIVERED`/`FAILED`) rows 3. Configurable retention duration and bounded batch deletion 4. Regression tests for cleanup and partial-failure scenarios This needs maintainer discussion on scope and priority before proceeding. --- *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]
