Aias00 opened a new issue, #808: URL: https://github.com/apache/rocketmq-dashboard/issues/808
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in GitHub Issues. - [x] I have searched the existing issues and believe this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository. ### Describe the Bug The Settings data source UI only exposes Prometheus, VictoriaMetrics, and Thanos in the type selector, but the backend already treats Mimir as a Prometheus-compatible data source type. Code evidence: - `server/src/main/java/org/apache/rocketmq/studio/settings/SettingsService.java` includes `mimir` in `PROMETHEUS_COMPATIBLE_TYPES`. - `web/src/pages/settings/index.tsx` only lists `Prometheus`, `VictoriaMetrics`, and `Thanos` in the data source type selector and tag color map. This makes Mimir effectively supported by the backend API but unavailable from the Studio UI. ### Expected Behavior The data source settings UI should expose Mimir as a selectable Prometheus-compatible backend, and the UI tests should cover creating a Mimir data source. ### Scope RocketMQ Studio Track 1 / METRICS-01 Prometheus-compatible data source integration. ### Proposed Fix Add Mimir to the data source type selector and type tag color map, then add a focused frontend test that creates a Mimir data source through the UI. -- 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]
