The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/alert-gc-time-ratio has failed. Run started by GitHub user lizhimins (triggered by lizhimins).
Head commit for run: 0b2f881574b8efd9c851cdc69285cb6cb2543679 / unbridled-41 <[email protected]> fix(alert): fire the DLQ resend alert on the documented 5-minute window The bundled RocketMQDLQResendHigh rule announces "More than 10 dead-letter queue resends occurred in 5 minutes." but thresholds with rate(), which is a per-second value: rate(rocketmq_dlq_resend_count[5m]) > 10 so the rule actually required ~10 resends per second (about 3000 per 5-minute window) before firing. A queue that starts re-driving dead letters at a genuinely alarming rate — tens per minute — stays silent. The sibling rule for the same "more than N in a window" contract, rocketmq-consumer-rebalance.yaml, already uses increase(rocketmq_consumer_rebalance_times[5m]) > 10, which is what the annotation describes. Fix: increase(rocketmq_dlq_resend_count[5m]) > 10, in the generator, the shipped asset, and the dev-mode mirror. Tested: AlertRuleAssetServiceTest#dlqResendAlertShouldCountResendsOverTheDocumentedWindowTest pins the shipped expression (red on rate(), green after) and #generatorShouldUseSameDlqResendWindowExpressionTest pins the generator copy against it; the asset generator reproduces the checked-in YAML byte for byte. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37904837036 With regards, GitHub Actions via GitBox
