Is there something wrong with the function of message trace? 消息轨迹功能是否有点问题？

[Luokejin]

When I searched details of message trace function, I found that I couldn't get any response from message trace detail function whatever I click the button.

And then I debugger the source code, finding that the function named queryMessageTraceByTopicAndKey
in org.apache.rocketmq.dashboard.service.impl.MessageTraceServiceImpl.java, uses the api of mqAdminExt.queryMessage whose parameters are 'topic' and 'key'.


But the point is that the request parameters from frontend are 'topic' and 'message ID'.
I can't figure out whether there is something wrong with this function of message trace. I wish that someone can teach me how to get the message trace detail from RocketMQ. Thanks, guys.

我最近在用dashboard那个消息轨迹详情功能的时候，发现怎么点那里都返回没有该消息轨迹详情。
然后我debugger源码的时候发现，进去到的方法queryMessageTraceByTopicAndKey里面用到的mqAdminExt.queryMessage 的API传入的参数是‘topic’和‘key’, 但实际上前端传进去的应该是'topic'和'messageID'的参数。
我在想是不是源码有问题，所以请教一下各位，我应该怎么写才能获取到消息轨迹详情？

[onejimmyboy]

消息轨迹会存在trace_topic里面，待查询的消息ID在trace_topic里面是作为key对应起来的。所以最后差的时topic和key，应该是这样的。你看看默认的trace_topic里面的消息，就能看出啦