Aias00 opened a new issue, #2679: URL: https://github.com/apache/rocketmq-dashboard/issues/2679
## Problem Native alert processing only advances state for metric samples present in the current collection pass. A FIRING or ACKED fingerprint resolves only when the same fingerprint later receives a clear evaluation. When a broker, Topic, Consumer Group or other monitored object disappears from discovery, no follow-up sample is produced. Its alert state can remain FIRING/ACKED indefinitely and no RESOLVED event or recovery notification is emitted. ## Evidence - `server/src/main/java/org/apache/rocketmq/studio/ops/alert/NativeAlertProcessor.java:50` - `server/src/main/java/org/apache/rocketmq/studio/ops/alert/AlertStateMachine.java:87` - `server/src/main/java/org/apache/rocketmq/studio/cluster/metrics/collectors/ApacheRocketMqBusinessMetricsCollector.java:65` - `server/src/main/java/org/apache/rocketmq/studio/cluster/metrics/collectors/ApacheRocketMqClusterMetricsCollector.java:82` ## Expected behavior - Reconcile previously active fingerprints against a complete successful collection scope. - Resolve missing fingerprints only after enough evidence that the scope was collected successfully; collection failures must not produce false recovery. - Emit one RESOLVED event and recovery notification. - Cover deleted resource, partial collection failure and reappearing resource cases. -- 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]
