New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 762371 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Participants' hotlists:
Hotlist-1


Sign in to add a comment

Port component graphs to Chromium Dash

Project Member Reported by amineer@chromium.org, Sep 6 2017

Issue description

Component graphs should be ported to the Component page.
 
Cc: anatolid@chromium.org
Project Member

Comment 2 by bugdroid1@chromium.org, Sep 26 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/d41563e9f5e149e2077d5d1cc43941b469c0b6da

commit d41563e9f5e149e2077d5d1cc43941b469c0b6da
Author: Alex Mineer <amineer@google.com>
Date: Tue Sep 26 16:43:19 2017

Status: Fixed (was: Unassigned)
Graphs are now available in the staging instance at https://chromiumdash-staging.googleplex.com/.  Performance is still atrocious; Prasad will clean that up with  issue 762372 .

Note that the graphs are pretty much all flat right now - this is because the staging instance of Chromium Dash fetches staging Monorail data, which doesn't change.  Thinks should look OK when we deploy to prod.
Thanks, it looks good! Is it possible to add graphs on the first page (https://chromiumdash-staging.googleplex.com/components) too? I'd like to see the graphs for the whole of WebRTC in addition to individual components :)
Filed issue 773776 to track this request - I think we'll add this eventually, but probably not soon.
Ok, thanks for the update!

Sign in to add a comment