New issue
Advanced search Search tips

Issue 903532 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: 3
NextAction: ----
OS: Chrome
Pri: 0
Type: Feature

Blocked on:
issue 903376


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Monarch for builder-level performance

Project Member Reported by jclinton@chromium.org, Nov 8

Issue description

We need to capture a basic level of visibility into overall builder performance and failure rates to inform both CI oncaller rotation visibility and SRE support, when needed. This item is capturing refreshing our ChromeOS Monarch presence, using the right data sources (LUCI instead of CBuildBot), and ensuring that our simple, basic Viceroy dashboard is adjusted appropriately. We should also audit what alerts are in place and refresh/align to oncall needs. We will not—at this time—migrate to a new Monarch data silo. Instead, we should look for the majority of the information that we need from LUCI once we embrace their domain model. This item is blocked on exporting our real builder names to LUCI.

 
Labels: Disable-Nags
EstimatedDays: 3
Estimate is based on the information being available via LUCI metric collections.  Once available we'll be able to provide quick views to overall pool health as well as proactive monitoring for individual bots.  

This bug will track the validation, dashboards, and monitoring efforts.  
Cc: mikenichols@chromium.org
 Issue 848886  has been merged into this issue.

Sign in to add a comment