yuluo-yx opened a new pull request, #4406:
URL: https://github.com/apache/rocketmq-dashboard/pull/4406

   <!-- Make sure the base branch is `master`: that is the RocketMQ Studio 
trunk. -->
   
   ### Which Issue(s) This PR Fixes
   
   - Fixes #3200
   - Replaces #3201, closed by the branch switch in #4379.
   
   ### Brief Description
   
   This is a resubmission of #3201 against `master`, following the branch 
switch notice in #4379. The fork branch is unchanged; `master` is now the 
RocketMQ Studio trunk.
   
   ## Summary
   
   - analyze the currently loaded Message Explorer results without issuing 
extra queries
   - show Broker, queue, tag, producer/store host, and UTC-hour distributions
   - summarize message size buckets and missing metadata
   - disclose loaded/server coverage and server scan truncation explicitly
   - add filtered dimension CSV export and deterministic analytics tests
   
   ### How Did You Test This Change?
   
   ## 原提交验证记录
   - focused analytics and existing Message page suites: 19 tests passed
   - `npm run lint` (0 errors; 10 pre-existing warnings)
   - `npm run build` (8,040 modules transformed)
   - scope audit: 536 additions across 4 files
   
   Fixes #3200
   
   ### Checklist
   
   - [x] One coherent change; unrelated modifications are not bundled in
   - [x] Commit subject follows Conventional Commits (`feat:` / `fix:` / 
`refactor:` / `chore:` / `docs:` / `perf:`)
   - [x] Tests added or updated for non-trivial changes, test methods named 
`...Test`
   - [x] New UI text has both Chinese and English entries under 
`web/src/i18n/`, or the change does not add UI text
   - [x] Architecture constraints stay green (`mvn test` runs the ArchUnit 
checks), or the original verification scope is stated above
   - [x] New source files carry the ASF license header, or no new source files 
were added
   - [x] Documentation touched where behaviour changed (README / `docs/` / 
in-app help), or no documentation change was required
   


-- 
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]

Reply via email to