tju-yxq opened a new issue, #5563: URL: https://github.com/apache/rocketmq-dashboard/issues/5563
## Problem The consumer group health diagnostics utility (`utils/consumerGroupDiagnostics.ts`) returns **Chinese display text directly** — the status label (`消费组健康` / `需要关注` / `消费风险`), every issue's title and description (13 variants across 10 issue codes), and the five recommendation sentences. The consumer page renders these verbatim in the health tab, so an operator who switches the console to English still gets an entirely Chinese diagnosis — even after the page itself was localized (#5529). The codebase already has the correct pattern for exactly this situation: `utils/messageTraceDiagnostics.ts` returns `titleKey` / `descriptionKey` / `statusKey` plus interpolation `params`, and the page resolves them through `t()` (`message.tsx` renders `t(issue.titleKey, issue.params)`). Six diagnostics utilities predate that pattern and still return raw text; this one is the consumer-facing member of that family. ## Expected behavior `analyzeConsumerGroupHealth` follows the established key-returning contract: - `statusText` → `statusKey` (`consumerHealth.statusHealthy` / `statusWarning` / `statusCritical`) - each issue carries `titleKey`, `descriptionKey`, and optional `params` (topic, count, ratio, seconds, client) instead of `title` / `description` - `recommendations` → `recommendationKeys` - the consumer page's health tab resolves all of them through `t()` - the zh text is byte-identical to what the utility returned before, so Chinese-locale users see no change ## Notes - 34 new `consumerHealth.*` entries in `translations.ts` (3 status + 13 title/description pairs + 5 recommendations). - Interpolated values (topic name, queue count, skew ratio, delay seconds, client id, heartbeat threshold) move into `params`, so English gets grammatical sentences instead of concatenated fragments. -- 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]
