You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/08/06 02:05:17 UTC
[I] feat: resolve message trace by selected instance endpoint [rocketmq-dashboard]
Aias00 opened a new issue, #1070:
URL: https://github.com/apache/rocketmq-dashboard/issues/1070
## Problem
Message trace must resolve its RocketMQ admin calls from the selected Studio instance. Using a process-wide endpoint can return a trace from the wrong cluster or fail in multi-instance deployments.
## Proposed change
- Reuse `RuntimeAdminClientResolver` from #1058.
- Require and propagate `instanceId` through message trace API, service, provider, and page layers.
- Preserve current trace response and error semantics while scoping the runtime query to the selected endpoint.
- Add focused backend and frontend regression coverage.
## Dependency
Depends on #1058. Implementation starts after #1058 merges into `rocketmq-studio`, so this can remain an independent PR.
## Scope
Part of #982. Message query is explicitly excluded and tracked separately.
--
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] feat: resolve message trace by selected instance endpoint [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins closed issue #1070: feat: resolve message trace by selected instance endpoint
URL: https://github.com/apache/rocketmq-dashboard/issues/1070
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] feat: resolve message trace by selected instance endpoint [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins commented on issue #1070:
URL: https://github.com/apache/rocketmq-dashboard/issues/1070#issuecomment-5202258364
Resolved by #1082 (merged into rocketmq-studio as fb821990).
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] feat: resolve message trace by selected instance endpoint [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #1070:
URL: https://github.com/apache/rocketmq-dashboard/issues/1070#issuecomment-5199914315
**Issue Evaluation**
Category: `enhancement` | Status: **Evaluated**
**Feasibility:** Feasible
**Scope:** Dashboard message trace module, depends on apache/rocketmq-dashboard#1058
This is a well-structured feature request as part of the Studio instance endpoint selection effort (#982). The proposed changes are focused:
- Add `endpoint` parameter to `MessageTraceController.queryMessageTraceKey`
- Pass endpoint through `AdminCommandHelper.executeCommand` to `MQAdminStartup.main`
- Add E2E test coverage
The dependency on #1058 (endpoint selection UI) is correctly identified. Implementation approach is sound.
---
*Automated evaluation by RockteMQ-AI*
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org