yuluo-yx opened a new issue, #2952: URL: https://github.com/apache/rocketmq-dashboard/issues/2952
Problem The alert schema migration adds fingerprint as a nullable column, so existing alert rows can legitimately have no fingerprint. The notification suppression service uses the database id as the incident key whenever fingerprint is absent. A legacy FIRING row and its later RESOLVED row therefore become two unrelated incidents. Impact The old FIRING row remains active in the correlation window and can suppress a business notification even though the matching cluster incident has already resolved. Expected behavior Correlate legacy rows with a stable fallback identity derived from their rule and resource scope, while preserving fingerprint correlation for new rows. Scope Update the suppression service and add a regression test covering a legacy FIRING and RESOLVED pair. -- 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]
