Last Comment Bug 1286856 - Create a dashboard for tracking and analyzing try end-to-end times
: Create a dashboard for tracking and analyzing try end-to-end times
Status: ASSIGNED
:
Product: Testing
Classification: Components
Component: General (show other bugs)
: unspecified
: Unspecified Unspecified
-- normal (vote)
: ---
Assigned To: Kyle Lahnakoski [:ekyle]
:
:
Mentors:
Depends on: 1280633
Blocks: thunder-try
  Show dependency treegraph
 
Reported: 2016-07-14 08:21 PDT by William Lachance (:wlach) (use needinfo!)
Modified: 2016-09-13 09:00 PDT (History)
4 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description User image William Lachance (:wlach) (use needinfo!) 2016-07-14 08:21:35 PDT
I have become convinced that we need some kind of dashboard for tracking how long try-pushes are taking, as well as breaking down the *individual* components of particularly long-lived try pushes and jobs.

In the past we've done various experiments with gantt-chart-type views of jobs which are useful for understanding what might be going on with an individual push, but never a holistic picture of the entire system, which is essential for optimization (for example, wait times are heavily impacted by what other parts of automation are doing).

Something like new relic's analytics views might be interesting inspiration here, as it combines a view of overall load on the system with samples of particularly long queries for analysis.
Comment 1 User image Armen Zambrano - Back on March 27th [:armenzg] (EDT/UTC-4) 2016-09-13 08:54:15 PDT
From ekyle:
Working on showing the high level (90th? percentile), “end-to-end” times. The hope is to reveal the longest running chain of jobs and provide a drill-down to the steps that explain the numbers. This particular statistic may be dubious, however, it provides something to build an interactive UI for other statistics.

Note You need to log in before you can comment on or make changes to this bug.