tju-yxq opened a new issue, #2643: URL: https://github.com/apache/rocketmq-dashboard/issues/2643
## Problem The trace-query history records the message ID and original message topic, but it does not record the optional trace topic used by the lookup. A query against a custom trace topic therefore appears in history without the information needed to repeat it. When a user selects that history row, the UI replays the message lookup with the default trace-topic behavior. If the trace data exists only on the custom topic, the replay returns no trace or a different trace. The current message-detail path also does not carry the selected custom trace topic into its automatic trace request. ## Expected behavior - Persist the normalized custom trace topic with message-id trace history; keep it null for the default topic and for existing rows. - Return it from the history API and restore it when a history row is selected. - Use the restored topic for the subsequent trace request, without changing key-based history behavior or providers that use the default topic. - Upgrade existing installations safely by adding the nullable column without losing existing history. This is a trace-history correctness issue, not a new provider capability: the custom-topic lookup already works when run directly, but the persisted history does not preserve the lookup contract. -- 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]
