[dashboard] embed entire grafana dashboards in metrics page#56307
[dashboard] embed entire grafana dashboards in metrics page#56307eric-higgins-ai wants to merge 2 commits intoray-project:masterfrom
Conversation
Signed-off-by: eric-higgins-ai <erichiggins@applied.co>
There was a problem hiding this comment.
Code Review
This pull request refactors the Metrics page to embed entire Grafana dashboards instead of individual panels, which is a great change for improving performance and stability. The related code cleanup, such as removing the now-unused panel configurations and state management, is well-executed. The tests have also been updated accordingly.
I've found a couple of minor but important issues in the src URLs for the new iframes in Metrics.tsx. They use a potentially undefined grafanaOrgId and have a duplicated var-datasource parameter. I've left specific suggestions to fix these. Other than that, the changes look solid.
| or "" | ||
| ) | ||
| global_filters = global_filters_str.split(",") | ||
| if global_filters_str == "": |
There was a problem hiding this comment.
found this bug while trying to generate the latest dashboards with collapsible sections. If this string is empty then some queries in the dashboard contain ,, in their filters, which is invalid. I can split this into a separate PR if that's better
Signed-off-by: eric-higgins-ai <erichiggins@applied.co>
|
Thanks! A few UI suggestions:
@simran-2797, @scottsun94 , do you mind mocking up the UI? You can go with my suggestions or try something different. @eric-higgins-ai , let me know if you aren't comfortable doing more UI changes, we can have someone take over the PR as well. |
|
@alanwguo I'm happy to make the UI changes, and it's not that urgent for us (we're just using Grafana directly right now) so waiting for a UI design isn't a big deal. However, @kshanmol mentioned that they want this to be in as early a Ray release as possible, and I'm sure it will get done faster if you can handle it within Anyscale. If you'd rather have somebody else take it over for that reason then that's ok with me too. |
thanks, I'll let you know as the designs come out. in the meanwhile, can put the global_filters_str empty string fix as a separate PR? It's a nice fix and we can get that pushed through quickly. |
|
This pull request has been automatically marked as stale because it has not had You can always ask for help on our discussion forum or Ray's public slack channel. If you'd like to keep this open, just leave any comment, and the stale label will be removed. |
Hi @eric-higgins-ai, just wanted to update you that we decided to go ahead with this change ourselves while iterating on the new designs. I will raise a fresh PR soon and link it here. After that we can close this one. Thank you for the effort though, learned a bunch from you here & the end result looks great! |
|
No problem at all @kshanmol , thanks for taking it over! I agree that it's likely faster for you to handle internally at Anyscale The UI in your other PR looks great! I'll be looking forward to the change in an upcoming ray version 🎉 |
|
Closing since #57561 is now merged. Thanks @eric-higgins-ai for the idea and the initial implementation! |
Why are these changes needed?
This improves the performance and stability of the Metrics page on the Ray dashboard by embedding the entire Default and Data dashboards instead of individual graphs.
A few notes:
Screen.Recording.2025-09-06.at.2.54.36.PM.mov
Related issue number
closes #55499
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.