yuluo-yx opened a new issue, #3138: URL: https://github.com/apache/rocketmq-dashboard/issues/3138
## 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. -- 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]
