Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Studio][Bug] Alert rule list omits instance binding from MCP output

Open Beginner friendly
#7,340 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

@X-LightYear is already working on this.

Since Oct 23, 2026.

  • #7341 by @X-LightYear — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
api, backend

Research direction

Start by locating AlertRuleListItem.from(AlertRuleVO) and the catalog schema for rmq.alert.rule.list. Read the focused handler and output schema tests, then check how the projection and schema represent optional fields. Done when an instance-bound rule exposes instanceId in the serialized output and schema tests pass, while global rules can omit it.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Java
Stars
1.4k
Forks
717
Avg merge
2d 2h
Merged PRs (30d)
143

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/rocketmq-dashboard

All issues in apache/rocketmq-dashboard

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.