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

Issue 828518 link

Starred by 1 user
Status: Assigned
Owner:
jclinton@chromium.org
Cc:
akes...@chromium.org
█ pho...@chromium.org
mar...@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Buildbucket + swarming -> Monitoring

Project Member Reported by dgarr...@chromium.org, Apr 3 2018 
If our monitoring solution can directly import data from buildbucket and swarming, we can have detailed data about builder utilization, scheduled wait times, pass/fail rates that include recipe level failures, etc.

We can also break that information down by display_label (Legoland display groups), build_config, branch, etc.

I think we will soon need this to manage our fleet of swarming builders.

Comment 1 by dgarr...@chromium.org, Apr 3 2018

Cc: pho...@chromium.org mar...@chromium.org akes...@chromium.org
Labels: -Pri-3 Pri-2
Owner: jclinton@chromium.org
I understand that it's possible to build this into viceroy by building Django plugins that query the buildbucket and swarming APIs.

I have not yet investigated how existing monitoring is emitted from buildbucket and swarming.

Comment 2 by akes...@chromium.org, Apr 3 2018

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI

Comment 3 by mar...@chromium.org, Apr 5 2018 

I'm planning to revamp the whole Swarming monitoring after I'm done with feature requests :)

It's at go/swarming-monitoring-v2

Comment 4 by mar...@chromium.org, Apr 5 2018 

Note that Swarming doesn't care about a "build", only individual tasks, which is the right abstraction layer at this level.

Comment 5 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
►

Sign in to add a comment