X-LightYear opened a new issue, #7340: URL: https://github.com/apache/rocketmq-dashboard/issues/7340
## Problem The `rmq.alert.rule.list` MCP tool is documented and implemented as a platform-level listing. It returns both global alert rules and rules bound to individual Studio Instances, but its serialized item projection omits the rule's `instanceId`. ## Reproduction 1. Configure one global alert rule and one rule bound to `instance-a`. 2. Invoke `rmq.alert.rule.list` without filters. 3. Inspect the returned items. ## Expected behavior An instance-bound rule should identify its Studio Instance in the MCP response. A global rule may omit the field. ## Actual behavior The response contains the rule name, metric, threshold, and status, but not the binding. A planner cannot distinguish a global rule from an instance-bound rule or identify the target instance before a follow-up operation. ## Root cause `AlertRuleListItem.from(AlertRuleVO)` did not copy `AlertRuleVO.instanceId`, and the catalog schema did not declare the field. ## Scope The change is additive: preserve the existing fields and expose the optional instance binding in the MCP list projection and schema. ## Regression evidence The pre-fix serialized projection failed a deterministic assertion for `"instanceId":"instance-a"`; the focused handler and output-schema tests pass with the fix. -- 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]
