New issue
Advanced search Search tips

Issue 710488 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Add monitoring for chromium-cq-status

Project Member Reported by serg...@chromium.org, Apr 11 2017

Issue description

We haven't noticed that the app was returning 500's for 5 days. We should add monitoring to this app.
 
Labels: cit-pm-40
Cc: dsansome@chromium.org
+1.  Let me know if you need help.
tAndrii has suggested to kill this app instead. Users has reported that the app was broken after 3 business days only and only because it broke autoroller, so I am not sure if it's used much. One of the apps that is using it atm is chromium-try-flakes and it is being rewritten using BQ pipeline right now, so I hope that we'll remove this dependency in the coming couple of weeks.
Actually app seems to be used quite actively (see attached graph): 334 page views per business day in the last 30 days. Not sure why users did not report an issue sooner, but killing this app without finding a replacement is not a good idea.
1UAjCovpDnJ.png
22.8 KB View Download
Owner: serg...@chromium.org
Status: Assigned (was: Available)
P1 with no owner is a no-go.
Owner: ----
Status: Available (was: Assigned)
I won't have time to fix this any time soon, so IMHO keeping it unassigned leaves a possibility for someone else to take it. I am also neither the owner nor the maintainer of the chromium-cq-status app.
Cc: serg...@chromium.org
1. I agree that Pri1 should be assigned. I disagree that this is Pri1.

2. +sergiyb@: can you mark this bug blocked on the bug that is about eliminating the need of CQ status app? Also, are those real pageviews by people only OR does it include endpoint access to fetch json data?
Owner: sergeybe...@chromium.org
Status: Assigned (was: Available)
https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/services.md#chromium_cq_status says sergeyberezin so assigning to him!
I don't know if there a bug about removing chromium-cq-status. The pageviews are by people since they come from Google Analytics and JSON endpoints won't be recorded.
I've assigned P1 to this bug simply bcz it's a follow up in a PM. AFAIK this is our policy. Apart from that, I also think this should not be P1.
What's the ETA for getting around to doing this? It's a P1 from a post mortem.
Components: -Infra>CQ Infra>Platform>CQdaemon
Labels: -Pri-1 Pri-2 Type-Feature
Labels: -Type-Feature Type-Bug

Comment 15 by efoo@chromium.org, Aug 31 2017

Components: Infra>Platform>CQ

Comment 16 by efoo@chromium.org, Aug 31 2017

Components: -Infra>Platform>CQdaemon
Cc: -serg...@chromium.org -dsansome@chromium.org sergeybe...@chromium.org
Owner: ----
Status: Available (was: Assigned)
Realistically, I'm not working on it, and won't get to it in any reasonable time. Making available, please re-triage if needed.

Comment 18 by efoo@chromium.org, Jun 2 2018

Cc: jbudorick@chromium.org
+jbudorick. This is a blocking bug for cit-pm-40. Is this still needed? Please comment. 
Status: Archived (was: Available)
My inclination is to not invest in chromium-cq-status at this time.
Indeed. Findit team has been working to get elimiate their dependency on it.

Sign in to add a comment