-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Update plank dashboard to filter and group by more things #19007
Update plank dashboard to filter and group by more things #19007
Conversation
Allow someone to filter and group by: - cluster - org - repo - state - type Add a third graph panel, and change each graph panel to group by user-selectable labels I intially had a graph panel for each of these, but: - it's a lot of clutter - it appeared to be timing out prometheus at the 90d range It turns out each template re-queries prometheus (serially) anytime the dashboard's time-range changes, and only after templates are refreshed do queries fired off for the dashboard's panels in parallel. This is necessary because the `label_values` prometheus query is time-range dependent. To mitigate this I changed the "type" and "state" templates to use a hardcoded list of values, since I think it unlikely we're going to add new prowjob types or states.
Part of #18785 |
FYI @kubernetes/ci-signal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thanks for adding this @spiffxp!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hasheddan, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Allow someone to filter and group by:
Add a third graph panel, and change each graph panel to group by
user-selectable labels
I intially had a graph panel for each of these, but:
It turns out each template re-queries prometheus (serially) anytime the
dashboard's time-range changes, and only after templates are refreshed do
queries fired off for the dashboard's panels in parallel. This is necessary
because the
label_values
prometheus query is time-range dependent.To mitigate this I changed the "type" and "state" templates to use a hardcoded
list of values, since I think it unlikely we're going to add new prowjob types
or states.
This required #19004 to
merge first so I could use
template.custom