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

Issue 798444 link

Starred by 1 user
Status: Fixed
Owner:
█ katthomas@chromium.org
Last visit > 30 days ago
Closed: Jan 2018
Components:
EstimatedDays: 1
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Move dataflow builder failure alert to chrome_ops_frontend and add playbook entry

Project Member Reported by katthomas@chromium.org, Jan 2 2018 
Right now there is a generic alert for the scheduler. With the trooper split, we should make a template for this so alerts for specific builders can go in the appropriate place. Also we should link to the template from the documentation.

Comment 1 by katthomas@chromium.org, Jan 3 2018

Summary: Move dataflow builder failure alert to chrome_ops_frontend and add playbook entry (was: Make template for dataflow job scheduler builder failure alert)
After thinking about this some more, I think it makes sense to keep a generic alert that the monitoring team can respond to. The monitoring team should be more familiar with the recipe. If necessary, the monitoring team can pass off the issue to the owner of a specific builder. 

That said, the alert was moved to chrome_ops_client_infra, but belongs in chrome_ops_frontend. Updating this bug accordingly. 

http://google3/configs/monitoring/chrome_ops_client_infra/buildbot_alerts.py?l=841&rcl=179114379

Comment 2 by katthomas@chromium.org, Jan 3 2018

Status: Started (was: Assigned)

Comment 3 by katthomas@google.com, Jan 9 2018

Status: Fixed (was: Started)
►

Sign in to add a comment