Aias00 opened a new issue, #1017: URL: https://github.com/apache/rocketmq-dashboard/issues/1017
## Problem\nDiagnostic and persisted operational data has several integrity gaps:\n- Message trace parsing receives a target message ID but does not use it to filter parsed trace lines.\n- Message and trace query history is inserted indefinitely with no retention policy or cleanup boundary.\n- K8s certificate persistence silently converts malformed enum/SAN data to null or an empty list.\n- Live topic/consumer detail queries can convert per-resource admin failures into normal-looking zero values.\n\n## Expected behavior\nDiagnostics must retain only bounded history, expose data corruption/unavailable state explicitly, and avoid attributing unrelated trace lines or failures to healthy resources.\n\n## Acceptance criteria\n- Trace parsing keeps only records for the requested message ID.\n- Query history has a configurable bounded retention/cleanup strategy.\n- Malformed persisted certificate fields are diagnosed rather than silently erased.\n- Resource-level admin failures are disti nguishable from zero lag/TPS.\n- Regression tests cover each error path. -- 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]
