iloveeyjafjalla opened a new issue, #6677:
URL: https://github.com/apache/rocketmq-dashboard/issues/6677

   ### 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 窗口聚合 select in the alert rule editor shows the API codes LAST / MAX / 
MIN / AVG / SUM as its option labels, while every other field of the same form 
is named (规则名称, RocketMQ 实例, 监控指标, 阈值条件, 持续时间, 重提醒间隔, 窗口秒数, 连续采样次数, 通知渠道). LAST 
in particular does not say what it aggregates - it means the newest sample in 
the window - so an operator has to guess what the rule will evaluate.
   
   The backend validates the value (AlertRuleRequestDTO rejects anything else 
with "aggregation is invalid"); the console simply renders the accepted codes 
unnamed.
   
   ### Steps to Reproduce
   
   1. Open 集群告警 (Ops -> Alert Rules).
   2. Click 新建规则 (or edit an existing rule).
   3. Open the 窗口聚合 select and read its options.
   
   ### What Did You Expect to See?
   
   The five accepted values named for the console (最近一次 / 最大值 / 最小值 / 平均值 / 总和, 
Latest / Maximum / Minimum / Average / Sum), with the payload sent to the API 
unchanged.
   
   ### What Did You See Instead?
   
   LAST, MAX, MIN, AVG and SUM rendered verbatim - in Chinese mode and in 
English mode alike.
   
   ### Additional Context
   
   Reproduced on e2f815fbf6ee8c9b90e32ce59d6e74f27b0c4ad4 while creating a 
cluster rule:
   
   - the select's default value reads LAST next to the localized 窗口聚合 label, 
and its dropdown lists LAST, MAX, MIN, AVG, SUM
   - the values come from web/src/pages/ops/alerts.tsx: the aggregation 
Form.Item builds its options from a raw string array ['LAST', 'MAX', 'MIN', 
'AVG', 'SUM']
   - the dictionary names the field (alerts.windowAggregation) but carries no 
entry for the five values, unlike the neighbouring duration and 
reminder-interval selects whose literals (5m, 30m) are self-describing
   
   ### 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]

Reply via email to