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

Issue 681043 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature

Blocked on:
issue 642297
issue 642298
issue 682235



Sign in to add a comment

CQ console

Project Member Reported by katthomas@chromium.org, Jan 13 2017

Issue description

A viceroy console consolidating monitoring information on CQ that will be useful for diagnosing issues. It may also be useful for prioritizing CQ reliability and performance improvement work. This will include adding alerts, where appropriate. This console is intended to be a starting point, and will need to be tuned and tweaked over time as we discover information is missing or thresholds are off. 

End State
- Consolidate current metrics on CQ
- Add any metrics/alerts that are identified as useful for debugging in the process of CQ reliability and performance work
- Update go/trooper-playbook
 
Blockedon: 642298
Blockedon: 642297
Labels: -Pri-2 Pri-1
Owner: katthomas@chromium.org
Status: Assigned (was: Available)
By the way, see go/cq-console for the project doc and an updated description of end state.
Blockedon: 682235
Status: WontFix (was: Assigned)
Marking this as WontFix for now. It's not high priority.

Sign in to add a comment