The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/cloud-queue-metric-catalog has failed. Run started by GitHub user Frun1na (triggered by Frun1na).
Head commit for run: aec55273f3c2320abae2a83ca00e4724d70dd7f8 / Apulupie <[email protected]> fix(alert): stop offering the cloud queue maximum no cloud collector measures #6184 made CloudRocketMqBusinessMetricsCollector publish consumer.lag.max_queue as UNSUPPORTED only, because the Aliyun and Tencent progress rows are per-topic aggregates without queue offsets - but the capability catalog still listed the metric for cloud instances, so the rule editor offered it and validate() accepted it. AlertRuleEvaluator reports an UNSUPPORTED sample as matched with the condition unmet, so such a rule could never fire. Drop the metric from BUSINESS_CLOUD, which is what the catalog serves for a cloud instance, and correct the design doc's source column for the metric; an Apache instance keeps the metric - its collector derives the maximum from real per-queue offsets - and the other cloud metrics are untouched. Existing stored rules are not migrated (the follow-up note in #6184 leaves that decision open). Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38340792341 With regards, GitHub Actions via GitBox
