Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS cost attribution (2c.2/4): [Spike 2h] Figure out how to define an infinity query variable #4944

Closed
2 tasks done
Tracked by #4872
GeorgianaElena opened this issue Oct 4, 2024 · 3 comments · Fixed by #4949 or #4953
Closed
2 tasks done
Tracked by #4872
Assignees

Comments

@GeorgianaElena
Copy link
Member

GeorgianaElena commented Oct 4, 2024

See #4934 (comment) for context

Definition of Done

  • there are panels of cost per component per hub correctly being rendered
  • there is a variable defined in grafonnet, similar to the one created by hand in the openscapes grafana

Image

@consideRatio
Copy link
Member

As part of going for this, I went for jupyterhub/grafana-dashboards#142 as the grafonnet docs are only available for that version, and I also didn't want to invest time exploring whats available in an older version when it could boil down to needing the new version.

@consideRatio
Copy link
Member

consideRatio commented Oct 4, 2024

For things to work properly, we actually needed grafonnet v11.1.0, so I figure I want to verify things work after we have jupyterhub/grafana-dashboards#142 merged. It worked when I did things locally though.

@consideRatio
Copy link
Member

Verified success!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants