Loyal-Young opened a new issue, #6450: URL: https://github.com/apache/rocketmq-dashboard/issues/6450
### Branch / component `rocketmq-studio`, alert request validation and Prometheus YAML export. ### Reproduction Create a rule with duration `1s1m` or `1m1m`. The request's `PROMETHEUS_DURATION_REGEXP` accepts both, and the exporter writes that value verbatim into `for:`. Prometheus rejects it: units must occur once and in decreasing order. An invalid rule file prevents loading the exported configuration. Prometheus's parser enforces this in [model/time.go](https://github.com/prometheus/common/blob/main/model/time.go), using strictly increasing unit positions. ### Expected / proposed scope Require descending, non-repeated units for the Prometheus-compatible duration field and preserve valid compounds such as `1h30m` and millisecond suffixes. The exporter already shares this validation pattern and has a fallback for invalid legacy values; apply the same order check there. Keep native reminder-interval parsing unchanged. I searched existing duration-related PRs; the matching Metrics step validation fixes cover another input path. I plan request-validation and export regressions for repeated/reversed units and valid compounds. ### AI assistance AI assistance was used to inspect the validation/export paths and compare them with Prometheus's duration parser. -- 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]
