Aias00 opened a new issue, #1004: URL: https://github.com/apache/rocketmq-dashboard/issues/1004
## Problem The metrics range-query API validates only that `start`, `end`, and `step` are present and ordered. It then reads the entire Prometheus response into a `JsonNode` and materializes every returned series and sample. A broad time range with a small step or high-cardinality PromQL can therefore allocate an unbounded response in Studio, causing excessive latency or memory pressure. ## Expected behavior - Parse and validate the Prometheus step before issuing the upstream request. - Reject requests whose requested sample-point budget exceeds a documented server-side limit. - Return a structured client error before contacting Prometheus. - Cover valid duration and numeric-second step formats, invalid steps, and oversized ranges with tests. ## Scope This change limits Studio request size only. It does not rewrite PromQL or replace upstream Prometheus query limits. ## Track Track 1 / METRICS-01 Prometheus data-source integration. -- 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]
