Metrics Query Visualizations

[MushuEE]

What would you like to be added:
We currently have a number of Queries that pull data from Kettle's BigQuery database. These metrics are helpful but not often looked at as it is hard to dig into as a human.

This feature would leverage Data Studio which has native BQ integration to add some more human visuals and graphs. I have setup duplicates of our custom queries as data sources and set them to refresh the data cache every 12 hours.

We are able to embed these reports:

<iframe width="600" height="800" src="https://datastudio.google.com/embed/reporting/1b8ea164-cd3f-46bc-9acd-27fb4f128c6c/page/1M" frameborder="0" style="border:0" allowfullscreen></iframe>

Which should allow me to host the view in something like Triage or Gubernator. Though the latter might be EOL at some point. A Metrics Overview Page could be added that just shows this embedded view.

Why is this needed:
We have no nice consolidated location for metrics that /sig-testing cares about.

/area metrics
/cc @spiffxp @BenTheElder @amwat @RobertKielty

Initial ideas on contents:

• Graph/tables of top consistent failures
• Graph/tables of top Flakes
• Graph/tables of activity
• Graph/table of Overall Pass/Fail

[MushuEE]

/assign

[aojea]

/cc

[MushuEE]

Notes:

• Flake Drill Down Options
  • This is possible but needs more reading into https://support.google.com/datastudio/answer/9319405?hl=en
• Time Filtering Options
  • This is possible but may require query edits to include dates for filtering as I do not think all queries by default include time info

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale
Since @MushuEE mentioned looking back into this offline

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[spiffxp]

/reopen
/remove-lifecycle rotten
/lifecycle frozen

[k8s-ci-robot]

@spiffxp: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[spiffxp]

Currently I think this lives in a google.com data studio instance, I would like to see what it'd take to recreate this in the community-owned kubernetes.io data studio instance: kubernetes/k8s.io#1590

[spiffxp]

/sig testing