pilichoumao opened a new issue, #6894: URL: https://github.com/apache/rocketmq-dashboard/issues/6894
### Description On `rocketmq-studio` at `a92c23144408cdf5729707050e9ecd9b75f1bad0`, Prometheus-compatible range query responses preserve `warnings` but drop the HTTP API's separate `infos` annotations. `AbstractPrometheusCompatibleMetricsSource.parseResponse` only copies warnings; `MetricDataVO`, the web API type, and MetricsExplorer cannot carry or display infos. These annotations explain potential query/data issues even when the request succeeds. For example, Prometheus can report that histogram_quantile repaired non-monotonic bucket counts. Operators currently see the values without that explanation, including when an annotated query returns no series. ### Reproduction Return a successful matrix response with `infos: ["input to histogram_quantile needed to be fixed for monotonicity"]` from a loopback query_range endpoint, and call the production `query` method. The serialized Studio response drops infos while retaining series and warnings. ECS research against the exact production parser: two annotated cases fail, two controls pass. A minimal propagation prototype preserves all four cases and passes the 21 existing PrometheusMetricsSource tests. This used an HTTP fixture, not a live Prometheus or ARMS service. ### Expected behavior Preserve infos separately from warnings, render them as informational notices (also for an empty result), and tolerate responses from compatible backends/older Studio servers that omit infos. Do not change query success, samples, or warning severity. Reference: https://prometheus.io/docs/prometheus/3.12/querying/api/ -- 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]
