Consider firing alerts on a smaller percentage of infra flakes to detect outages earlier |
||||||||
Issue description
,
Mar 1 2017
Yes it is. I can take it, too. Thank you for bringing it to my attention.
,
Mar 23 2017
Moved to Infra>CQ since this is a CQ specific alert update. Added label "Ops-AddMonitoring" to track monitoring tasks over services.
,
Mar 23 2017
This is not CQ specific because it applies to waterfall as well. Are we trying to avoid using the Infra>Monitoring label?
,
Sep 7 2017
The Infra>Monitoring component should only be used for the monitoring backend. This is a alerts tuning issue which should be fixed under the related service area. Specifying Infra>Client>Chrome
,
Sep 7 2017
Hey Katie, this is blocking closing of cit-pm-18. Any updates on this?
,
Sep 7 2017
I haven't been working on it because it is relatively low priority.
,
Sep 7 2017
#6: do P2s block closing PMs? I thought the policy was focused on P1s, but perhaps I misunderstood it.
,
Nov 16 2017
I'm sending this over to Platform. I think infra failures and related monitoring should be owned by that team, but I'm happy to advise if someone picks this up!
,
Jun 2 2018
This is a blocking bug for cit-pm-18. +amcrae. Would someone be picking this up from your team?
,
Oct 1
this is essentially done: https://cs.corp.google.com/piper///depot/google3/configs/monitoring/chrome_ops_client_infra/luci_config.py?q=luci_config.py+f:&g=0&rcl=214865471&l=65 reopen if incorrect |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by benhenry@chromium.org
, Mar 1 2017Components: -Infra Infra>Monitoring
Labels: cit-pm-18 Type-Bug
Status: Available (was: Untriaged)