kuberay
kuberay copied to clipboard
fix: avoid hard-code Prometheus datasource id
Why are these changes needed?
Currently the kuberay-api-server and kuberay-controller-runtime Grafana dashboard hard coded the Prometheus data source id, which is not re-usable by people. Fixed the hard code.
Related issue number
Checks
- [x] I've made sure the tests are passing.
- Testing Strategy
- [ ] Unit tests
- [x] Manual tests
- [ ] This PR is not tested :(
Would you mind providing more details about how you test this PR manually? These two files are not mentioned in the Ray documentation. In addition, these files haven't been updated for two years, so I am unsure whether they work or not. I need to manually test this PR.
Thanks @kevin85421 . Steps include,
- Setup the Prometheus and Grafana. follow this doc
- In Grafana, import the dashboard as the snapshot. Copy and past the Json mentioned and import
cc @Yicheng-Lu-llll would you mind reviewing this PR?
Setup the Prometheus and Grafana. follow this doc
The document doesn't include any service monitor or Pod monitor for the KubeRay operator Pod. Is Prometheus able to fetch the metrics?