RockteMQ-AI commented on issue #2532: URL: https://github.com/apache/rocketmq-dashboard/issues/2532#issuecomment-5376939521
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** feasible **Scope:** Alert subsystem (backend alert domain, metric collection, UI alert pages), dashboard replica coordination **Compatibility:** No breaking changes — preserves existing Prometheus integration paths This is a well-scoped enhancement that addresses a real gap: cluster alert evaluation currently depends on Prometheus, leaving installations without it unable to use cluster alerts natively. The proposed approach — introducing a native RocketMQ metric collection path alongside existing Prometheus integrations — is architecturally sound and backward-compatible. Key considerations for implementation: - **Metric collection coordination across replicas**: needs a clear leader-election or partition strategy to avoid duplicate collection - **State persistence**: alert state transitions and acknowledgement require durable storage; consider whether the existing dashboard DB schema can accommodate this or needs migration - **Rule testing**: a dry-run/preview mode for alert rules would improve UX and reduce misconfiguration risk - **Backward compatibility**: the three existing menu entry points should continue to work unchanged during and after migration This enhancement is ready for maintainer discussion and prioritization. --- *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]
