New issue
Advanced search Search tips

Issue 849289 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Aug 27
Cc:
hinoka@chromium.org
estaab@chromium.org
efoo@chromium.org
no...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Monitor HTTP 500s

Project Member Reported by no...@chromium.org, Jun 4 2018 
context:  bug 843393 
oncall was not notified about the issue. Change HTTP 500s thresholds. HTTP 500s for HTML pages, accessed by humans, are less tolerable than transient errors in RPCs.

Comment 1 by no...@chromium.org, Jun 4 2018 

from  bug 843393 : hinoka@:

500s on backends (cron / pubsub) aren't expected, but are acceptable.  They're usually due to datastore (or memcache, if ds_cache is on strict) flakes.

500s on prpc endpoints aren't expected nor ideal, but aren't usually user-visible

500s on frontends aren't expected nor acceptable, but setting the threshold too low will alerts us on things that aren't always actionable (eg. short term datastore flake, gerrit flake).

Comment 2 by qyears...@chromium.org, Jun 14 2018

Owner: qyears...@chromium.org
Status: Assigned (was: Available)
Summary: Monitor HTTP 500s (was: monitor HTTP 500s)

Comment 3 by qyears...@chromium.org, Jun 15 2018

Status: Started (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 15 2018 

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

commit 6f9c030d6a208da27f8a198cf74a357051c490ab
Author: Quinten Yearsley <qyearsley@chromium.org>
Date: Fri Jun 15 18:04:35 2018

Comment 5 by qyears...@chromium.org, Jun 27 2018 

Monitoring change now committed and should be active, sending alerts to staging email address.

Comment 6 by qyears...@chromium.org, Aug 25

Owner: ----
Status: Available (was: Started)

Comment 7 by no...@chromium.org, Aug 27

Status: Fixed (was: Available)
i believe the original problem was sufficiently fixed by the new alert rule and the follow up is bug 857512, so this can be closed
►

Sign in to add a comment