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

Issue 760703 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Merge codesearch playbook into trooper playbook

Project Member Reported by zhangtiff@chromium.org, Aug 30 2017

Issue description

On my last trooper shift, I was somewhat confused by the CrawlAttemptFailureRatioTooHigh entry ( https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/troopers/playbook.md#CrawlAttemptFailureRatioTooHigh ) because there's a lot of alert headers before it links to the Codesearch playbook, and some of the alerts in between have text in their entries, making it hard to tell that the  Codesearch alert entries are linked to the playbook link. 

It would be nice to merge the codesearch playbook into the main trooper playbook if possible. Otherwise, a simpler fix for now would be to rearrange the headers, so it's more clear that the codesearch alerts have their own playbook. 


 

Comment 1 by emso@chromium.org, Sep 1 2017

Owner: emso@chromium.org
Status: Assigned (was: Untriaged)
Yes, that's confusing. The list has also been interrupted by two GCEBackendTaintedVersion* alerts. 

I'll update the code search alerts to link directly to the code search playbook instead of to the chrome infra playbook. There is a lot of stuff in the code search playbook and it is easier to edit it in the current doc. While we remain on the current infrastructure, I think it's better to keep the playbook in the doc. 
Project Member

Comment 2 by bugdroid1@chromium.org, Sep 1 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/9b7eab46607044ae6acb3318cbeff2ec1d36a1c8

commit 9b7eab46607044ae6acb3318cbeff2ec1d36a1c8
Author: Emma Soederberg <emso@google.com>
Date: Fri Sep 01 18:59:31 2017

Comment 3 by emso@chromium.org, Sep 5 2017

Status: Fixed (was: Assigned)

Sign in to add a comment