You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2021/09/09 07:46:12 UTC
[GitHub] [rocketmq-dashboard] zhangjidi2016 opened a new issue #19: Message track query enhancement
zhangjidi2016 opened a new issue #19:
URL: https://github.com/apache/rocketmq-dashboard/issues/19
Currently, system topic (RMQ_SYS_TRACE_TOPIC) or message track defined in configuration files are used by default for message track query on the console. But now, users can specify specific topic to save message track information when sending and receiving messages on the client. If so, The console cannot query this message track information.
Can we select the previously specified message track topic before the user queries the message track information, like this? @StyleTang @vongosling
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-dashboard] StyleTang closed issue #19: Message track query enhancement
Posted by GitBox <gi...@apache.org>.
StyleTang closed issue #19:
URL: https://github.com/apache/rocketmq-dashboard/issues/19
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-dashboard] StyleTang commented on issue #19: Message track query enhancement
Posted by GitBox <gi...@apache.org>.
StyleTang commented on issue #19:
URL: https://github.com/apache/rocketmq-dashboard/issues/19#issuecomment-916915250
I get it, you are right, It is necessary to let users choose the msgTrackTopic by themselves.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-dashboard] StyleTang commented on issue #19: Message track query enhancement
Posted by GitBox <gi...@apache.org>.
StyleTang commented on issue #19:
URL: https://github.com/apache/rocketmq-dashboard/issues/19#issuecomment-916157916
I think choosing a track message topic manually is not a good user experience.
Users rarely modify msgTrackTopic, we have a rocketmq.config.msgTrackTopicName config to use a specific message track topic.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-dashboard] zhangjidi2016 commented on issue #19: Message track query enhancement
Posted by GitBox <gi...@apache.org>.
zhangjidi2016 commented on issue #19:
URL: https://github.com/apache/rocketmq-dashboard/issues/19#issuecomment-916536296
Yes, msgTrackTopic rarely set, but if different users on the client side using different msgTrackTopic In the same cluster, and rocketmq. config. msgTrackTopicName in rocketmq-dashboard can be set only one. I think we should consider this situation.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org