RockteMQ-AI commented on issue #4840: URL: https://github.com/apache/rocketmq-dashboard/issues/4840#issuecomment-5770639859
**Issue Evaluation** Category: `bug` | Status: **Confirmed** This is a valid timezone handling defect. The `lastTriggered` timestamp from the server is a UTC-naive ISO string, but `new Date()` interprets it as browser-local time. For viewers in UTC+8, a rule triggered at 15:00 UTC (displayed as `2026-09-21T15:00:00`) gets parsed as 15:00 local time (07:00 UTC), shifting it outside the 24-hour window and undercounting the stat. **Root Cause:** The `new Date(isoString)` constructor treats a `YYYY-MM-DDTHH:mm:ss` string (no Z/suffix) as local time per ECMAScript spec, not UTC. **Impact:** The 'Triggered in 24h' stat on the alerts page undercounts for all non-UTC viewers, with the magnitude equal to the viewer's UTC offset. **Severity:** Medium — data accuracy issue for a monitoring dashboard. The referenced PR #4835 correctly appends a `Z` suffix before parsing. --- *Automated evaluation by RockteMQ-AI* -- 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]
