RockteMQ-AI commented on issue #3104:
URL: 
https://github.com/apache/rocketmq-dashboard/issues/3104#issuecomment-5535969891

   **Issue Evaluation**
   
   Category: `bug` | Status: **Confirmed**
   
   Thank you for the detailed report. The cross-metric state reconciliation 
defect in native alert processing is a valid bug.
   
   **Root Cause:** `NativeAlertProcessor.reconcileMissingActiveStates` builds 
`presentKeys` using scope matching (instance + resource labels) without 
verifying that the sample's metric matches the rule's metric. This allows a 
different metric with the same labels to keep a missing metric's state active 
indefinitely.
   
   **Impact:** 
   - UI reports phantom incidents without active metric samples
   - Recovery notifications are never sent
   - Operator confidence in native alerting is degraded
   
   **Severity:** Medium-High (affects alert reliability, not message traffic)
   
   **Next Steps:** The suggested fix (adding `sample.metricKey() == 
rule.metric` check in the reconciliation loop) is the correct approach. An 
automated fix proposal will be generated. Reply `/approve` to proceed with PR 
generation.
   
   ---
   *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]

Reply via email to