coordination #152773
open[epic] Provide relevant squad metrics
50%
Description
Motivation¶
Follow-up of #118135 and other tickets.
For Progress we can use as starting point: https://rakoenig.github.io/qe-yam-backlog-assistant/
For openQA we could base them on: https://metabase.mae.suse.de/dashboard/60-openqa-results
Acceptance criteria¶
AC1: Provide metrics for Yam squad for progress and openQA
Additional information¶
@rainerkoenig did some research in hackweek, we should take a look basedon that as starting point.
Updated by rainerkoenig about 1 year ago
- Status changed from Workable to In Progress
Updated by JERiveraMoya about 1 year ago
- Subject changed from [epic] Provide relevant metrics for Yam squad to [epic] Provide relevant squad metrics
Updated by JERiveraMoya about 1 year ago
@rainerkoenig for openQA we could use this: https://metabase.mae.suse.de/dashboard/60-openqa-results
slack: https://suse.slack.com/archives/C02CANHLANP/p1704728201049709
please take a look when you have the time just to evaluate.
Updated by rainerkoenig about 1 year ago
Had a quick look at the metabase chart. Nicely shows the pain points, but
- I see a count of failures, but I don't have any idea when the counting started. So let us assume that we fix the problems in
installation, then what will happen? Counter remains at 374? It would be really helpful if this would be a "counts for the last week" or "counts for the last 4 weeks" or whatever, so that after fixing issues the testsuite or module would go down in this list. - This is a very global view, I'd love to have e.g. the entries that are our squad's responsibility highlighted in a different color.
Updated by okurz about 1 year ago
rainerkoenig wrote in #note-5:
Had a quick look at the metabase chart. Nicely shows the pain points, but
- I see a count of failures, but I don't have any idea when the counting started. So let us assume that we fix the problems in
installation, then what will happen? Counter remains at 374? It would be really helpful if this would be a "counts for the last week" or "counts for the last 4 weeks" or whatever, so that after fixing issues the testsuite or module would go down in this list.
The specific metabase "question" https://metabase.mae.suse.de/question/318-which-testsuites-fail-the-most-on-osd has the filters "t_created Previous 30 Days" and "result is failed" so it's effectively what you called "counts for the last 4 weeks". Obviously this can be changed based on specific needs.
- This is a very global view, I'd love to have e.g. the entries that are our squad's responsibility highlighted in a different color.
You should be able to create specific queries in metabase yourself to suit your needs.