apache / apache/rocketmq-dashboard
[Studio][Feature] Search Topic and Consumer Group resources across instances
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 683
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 58
Description
## Problem
Studio instance pages expose one RocketMQ instance at a time. Operators responsible for a fleet cannot answer basic placement questions such as “which instances contain this Topic?” or “is this Consumer Group deployed in disaster recovery?” without switching pages and exporting each inventory separately.
## Proposed behavior
Add a read-only fleet resource inventory from the Instance page that:
- scans selected instances for complete paginated Topic and Consumer Group inventories;
- limits concurrent instance work in small batches;
- preserves successful results and identifies the exact resource kind when another load fails;
- annotates same-kind resource names with every instance where they occur;
- supports name/configuration search plus kind, instance, vendor, and shared-name filters;
- exports exactly the visible rows as CSV.
## Acceptance criteria
1. Topic and Consumer Group names are counted independently.
2. Same-name placement includes the current and other instance ids.
3. Partial failures do not discard successful inventories.
4. A new load cannot be overwritten by an older response.
5. The table follows the project width helper and long values are truncated with full hover text.
6. Chinese and English UI text and focused regression tests are included.
## Scope
The inventory is observational. It does not create, update, copy, or delete RocketMQ resources.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the Studio Instance page and trace the existing Topic and Consumer Group inventory requests, pagination, table filters, and CSV export. Compare the current behavior with each acceptance criterion, then add focused regression coverage and Chinese and English UI text; done means visible fleet results remain correct under partial failures, filtering, and overlapping loads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100