You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/08/22 00:42:27 UTC
[I] [Studio] Add native RocketMQ cluster alert collection and event lifecycle [rocketmq-dashboard]
Aias00 opened a new issue, #2532:
URL: https://github.com/apache/rocketmq-dashboard/issues/2532
## Problem
Studio currently separates business alert rules, cluster alert rules, and alert events, but cluster alert evaluation depends on Prometheus rather than directly collecting RocketMQ runtime metrics. This leaves the feature incomplete for installations without Prometheus.
## Scope
- Introduce a native Apache RocketMQ metric collection path for cluster, consumer lag, and DLQ metrics.
- Persist metric snapshots and evaluate scoped cluster/business alert rules without external Prometheus.
- Persist alert state and transitions, provide acknowledgement, rule testing, collector health, and paged events.
- Preserve the existing three menu entry points while sharing backend alert domain infrastructure.
- Coordinate collection across dashboard replicas.
## Non-goals
- Replace existing Prometheus integrations.
- Add external notification delivery beyond existing integrations.
## Validation
- Unit/API coverage for collection, evaluation, state transitions, rule testing, pagination and UI flows.
- Existing Studio alert paths remain available.
--
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio] Add native RocketMQ cluster alert collection and event lifecycle [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins commented on issue #2532:
URL: https://github.com/apache/rocketmq-dashboard/issues/2532#issuecomment-5437063069
Resolved by #2533 (merged into rocketmq-studio as 358e6b67).
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio] Add native RocketMQ cluster alert collection and event lifecycle [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins closed issue #2532: [Studio] Add native RocketMQ cluster alert collection and event lifecycle
URL: https://github.com/apache/rocketmq-dashboard/issues/2532
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio] Add native RocketMQ cluster alert collection and event lifecycle [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org