Enable custom aggregating of Bug Count & SLO trends in groups of multiple components |
||||||
Issue descriptionChromium dash provides trends of bug counts and SLO violations per component. Teams work to triage multiple components. It would help to be able to view the data of multiple user-selected components combined. E.g. the device team has links to several dashboards: https://docs.google.com/spreadsheets/d/1yY3cU9_fzjX_NJ99DmwdUvx1o_SdXyNsXy9tPj2XxwM/edit for Blink>AmbientLight,Blink>Bluetooth,Blink>GamepadAPI,Blink>ImageCapture,Blink>Location,Blink>USB,Blink>WakeLock,IO>Bluetooth,IO>DeviceOrientation,IO>Gamepad,IO>USB Ideally a single dashboard for the team could be configured, trends viewed, and then if necessary the team could investigate each component individually.
,
Apr 14 2017
As you can see from the bug I just duplicated, this is functionality I'd like to provide - we can use this as the tracking bug since your description is much more thorough. FWIW, we're currently working to finish productionizing the dashboard (e.g. landing all code in a formal repo, security review, etc) so it might take us a while to get to this - but I do understand the need and plan to support it as soon as possible.
,
Apr 25 2017
Bonus points if we could autogenerate this grouping. We will soon have team mailing lists + bug components listed in OWNERS files in the repo. We should in theory be able to generate from that a mapping from team mailing list to all the bug components they're responsible for and show one entry in chromium dash for that team.
,
Apr 25 2017
,
Apr 25 2017
We already have this for Blink components and other teams are getting there as well, so we should definitely auto-generate this mapping.
,
May 20 2017
,
May 25 2017
+sergiyb, prasadv Rather than have a separate "Flakiness" page, perhaps we should implement this feature (by creating a "Teams" page which corresponds to the team mappings from code referenced in c#3), and then we could list test flakiness / disabliness on the same page along the other component stats? This would prevent users from having to visit multiple pages to get a holistic view of the data they care about. To everyone else (specifically scheib@) - if we implemented the "Teams" view such that it *only* used the team mappings referenced in code, would that satisfy your request? Or would you want the ability to create ad-hoc groupings on the fly?
,
May 27 2017
As discuss in a VC today, I think it's a good idea to integrate flakiness as health metric in a view broken by teams. I also think teams view should show overall stats, but also recurse into components. Finally, we need to find a way to show additional data besides the graphs such as list of directories and test suites owned by a team, their stats and a link to test-results app, so that users can dig deeper into flakiness.
,
Jan 31 2018
,
Sep 8
No longer on the Chrome team, e-mail me @google.com if any attention still required from me here, otherwise good luck! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by amineer@chromium.org
, Apr 14 2017