New issue
Advanced search Search tips

Issue 848886 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 903532
Owner:
Closed: Dec 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Blocking:
issue 864588



Sign in to add a comment

Implement longitudinal monitoring of build health on Swarming hosts

Project Member Reported by jclinton@chromium.org, Jun 1 2018

Issue description

Following on from  https://crbug.com/842018 , we need monitoring that tells us when a Swarming host is continually failing every build scheduled on it.

This is different from legacy Buildbot where the same build always ran on the same host: we monitored on build health. In Swarming, a single host may be used for many different builds and so a host issue that affects builds will not be seen unless we monitor for individual host failure rates.
 
Components: -Infra Infra>Platform>Swarming Infra>Monitoring
Status: Started (was: Assigned)
Doing some investigation now to find out what is available, as well as flexibility into crafting reporting to fit our specific needs.  

Will update as I have more information.

-- Mike
Blocking: 864588
Mergedinto: 903532
Status: Duplicate (was: Started)
There is a duplicate bug opened to track bot health via Swarming.  I feel like these end up tracking the same initiative therefore marking this as duplicate as the other bug is being tracked as part of the ParallelCQ effort. 

-- Mike

Sign in to add a comment