iloveeyjafjalla opened a new issue, #6671: URL: https://github.com/apache/rocketmq-dashboard/issues/6671
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: rocketmq-studio git commit id: e2f815fbf6ee8c9b90e32ce59d6e74f27b0c4ad4 deployed as: built from source (server/ + web/ dev server) against the docker stack in deploy/ ### Runtime Environment OS: Windows 11 24H2 MySQL: 8.x container (host port 13306) browser: Chromium, console served by the Vite dev server ### Connected RocketMQ Cluster RocketMQ version: 5.3.2 access mode: Direct to NameServer/Broker (namesrv 127.0.0.1:9876) deployment: docker (apache/rocketmq:5.3.2, single broker-a), console instance local-broker ### Build Toolchain JDK 21, Maven 3.9, Node.js 20.19.5 ### Describe the Bug The alert delivery surfaces print the API wire codes instead of names, on pages where everything else is localized. - Ops -> Alert Deliveries (/ops/alert-deliveries): the channel column renders "dingtalk" and the status column renders "DELIVERED" / "FAILED" / "RETRY_WAIT"; the channel filter offers "dingtalk / email / sms" and the status filter offers "PENDING / SENDING / DELIVERED / RETRY_WAIT / FAILED" as their visible option labels; the details drawer repeats both codes. - System Alerts: expanding the delivery-records panel on an alert card prints "dingtalk: FAILED (5)". The same table row therefore shows the localized "已投递" in the result column next to the raw "DELIVERED" in the status column, and the console asks a Chinese-reading operator to choose between PENDING and RETRY_WAIT. The API itself is fine - /api/system-alerts/deliveries/page returns {"channel":"dingtalk","status":"DELIVERED"} - only the rendering leaks the wire format. ### Steps to Reproduce 1. Settings: configure a DingTalk bot webhook reachable from the server. 2. Cluster Alerts: create a rule with metric broker.disk.usage_ratio, operator >, threshold 0, duration 0s, channel dingtalk, enabled. 3. Wait for the alert to fire, so the outbox writes a delivery row. 4. Open Ops -> Alert Deliveries: read the channel and status columns, open both filter dropdowns, then open one row's details drawer. 5. Open System Alerts and expand the delivery-records panel on the firing alert. ### What Did You Expect to See? The channel and the status named in the console language (钉钉/邮件/短信 and 已投递/等待重试/投递失败), the way the neighbouring result column, the column headers and the page subtitle already are. The values sent to the API must stay the wire codes. ### What Did You See Instead? dingtalk / DELIVERED / FAILED / RETRY_WAIT / PENDING / SENDING / sms / email rendered verbatim - in the table, in both filter dropdowns, in the details drawer and in the alert card's delivery timeline. ### Additional Context Reproduced on e2f815fbf6ee8c9b90e32ce59d6e74f27b0c4ad4 with a live delivery row (channel dingtalk, status DELIVERED): - list row: channel=dingtalk, status=DELIVERED, result column=已投递 - status filter options: PENDING, SENDING, DELIVERED, RETRY_WAIT, FAILED - channel filter options: dingtalk, email, sms - drawer: channel=dingtalk, status=DELIVERED - alert card timeline: dingtalk: DELIVERED (1) Rendering lives in web/src/pages/ops/notificationDeliveries.tsx (status column render, both Select option lists, the drawer) and web/src/pages/ops/systemAlerts.tsx (the delivery tag); the dictionary has no deliveries.status.* / deliveries.channel.* entries. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
