Aias00 opened a new issue, #1987: URL: https://github.com/apache/rocketmq-dashboard/issues/1987
### Track RocketMQ Studio Track 1: unified control plane / METRICS-01. ### Problem `SettingsService.testDataSource` probes every Prometheus-compatible backend through `/api/v1/query`. Runtime metrics queries already use backend-specific prefixes, including `/select/0/prometheus` for VictoriaMetrics and `/prometheus` for Mimir. As a result, a valid VictoriaMetrics or Mimir data source can fail the Settings connection test even though Studio can query it at runtime. ### Expected behavior - Select the instant-query path from the configured backend type. - Keep plain `/api/v1/query` for Prometheus, Thanos, Cortex, ARMS, and compatible defaults. - Use `/select/0/prometheus/api/v1/query` for VictoriaMetrics. - Use `/prometheus/api/v1/query` for Mimir. - Preserve the existing authentication, timeout, redirect, and SSRF protections. ### Acceptance criteria - Connection tests reach the backend-specific instant-query endpoint. - VictoriaMetrics and Mimir paths have regression coverage. - Provider type resolution remains locale-independent. ### Scope note This is distinct from #808, which exposed Mimir in the settings UI, and #1965, which handles untested data-source status. Neither aligns the settings-side test request with the runtime backend path contract. -- 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]
