Add monitoring for chromium-cq-status |
||||||||||||||
Issue descriptionWe haven't noticed that the app was returning 500's for 5 days. We should add monitoring to this app.
,
Apr 19 2017
+1. Let me know if you need help.
,
Apr 25 2017
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.
,
Apr 25 2017
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.
,
Apr 26 2017
P1 with no owner is a no-go.
,
Apr 26 2017
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.
,
Apr 26 2017
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?
,
Apr 27 2017
https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/services.md#chromium_cq_status says sergeyberezin so assigning to him!
,
Apr 27 2017
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.
,
Apr 27 2017
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.
,
May 24 2017
What's the ETA for getting around to doing this? It's a P1 from a post mortem.
,
Aug 18 2017
,
Aug 18 2017
,
Aug 18 2017
,
Aug 31 2017
,
Aug 31 2017
,
Oct 11 2017
Realistically, I'm not working on it, and won't get to it in any reasonable time. Making available, please re-triage if needed.
,
Jun 2 2018
+jbudorick. This is a blocking bug for cit-pm-40. Is this still needed? Please comment.
,
Jun 2 2018
My inclination is to not invest in chromium-cq-status at this time.
,
Jun 2 2018
Indeed. Findit team has been working to get elimiate their dependency on it. |
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by serg...@chromium.org
, Apr 11 2017