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

Issue 680626 link

Starred by 2 users
Status: Fixed
Owner:
█ katthomas@chromium.org
Last visit > 30 days ago
Closed: Apr 2017
Cc:
chrishall@chromium.org
dpranke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocked on:
issue 636614
issue 677591


Sign in to add a comment

Establish CQ SLO

Project Member Reported by katthomas@google.com, Jan 12 2017 
Umbrella bug to work related to establishing a Chromium Commit Queue SLO. We can consider the SLO "established" when we have defined it, are tracking it, have a process for responding to being out of SLO (may include alerts), and have tuned the SLO so it is performing its desired function: serving as a promise to Chrome developers and helping Chrome Operations prioritize work.

Comment 1 by katthomas@google.com, Jan 12 2017

Blockedon: 636614

Comment 2 by katthomas@google.com, Jan 12 2017

Blockedon: 677591

Comment 3 by katthomas@chromium.org, Jan 17 2017

Status: Started (was: Assigned)

Comment 4 by stip@chromium.org, Feb 10 2017

Cc: -stip@chromium.org

Comment 5 by katthomas@google.com, Mar 10 2017 

We're going to consider replacing the timeframes in our SLO definitions with "last N builds". First step is to see if/how we can do this in Mash.

Comment 6 by efoo@chromium.org, Mar 29 2017

Components: -Infra>Monitoring Infra>CQ
Labels: Ops-SLOs
Removing Infra>Monitoring since this is a CQ related item. Please reserve Infra>Monitoring for monitoring (ts_mon and event_mon) bugs. Added Ops-SLOs label to track SLO related tasks.

Comment 7 by katthomas@chromium.org, Apr 4 2017

Status: Fixed (was: Started)
This is done. See go/chromium-commit-queue-slo.

See  Bug 677591  for tracking work on the dashboard.

See Bug 636614 for tracking work on the SLA.
►

Sign in to add a comment