Clean up instructions for accessing CQ logs in trooper playbook |
||||||
Issue descriptionGo to: https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/troopers/playbook.md#CQResponseTimeHigh Instructions say go to go/chrome-infra-logs filter logName=“projects/chrome-infra-logs/logs/commit_queue.log” That appears to come up empty https://screenshot.googleplex.com/kkrn6xx0OQ9
,
Mar 10 2017
Query comes up as deadline exceeded https://screenshot.googleplex.com/ByPH6QxZ723 I suspect this broke from the logs v1 to v2 transition.
,
Mar 10 2017
From vadimsh: re cloud logs: unfortunately it now requires some button clicking and typing to get to CQ logs: https://screenshot.googleplex.com/rEJJtqCQtR2.png
,
Mar 10 2017
,
Aug 31 2017
,
Aug 31 2017
,
Nov 16 2017
tandrii, I think it makes more sense for you to take this.
,
Nov 16 2017
https://chrome-internal.googlesource.com/infra/infra_internal/+/master/infra_internal/services/cq/README.md#next-gen-cq-deployment already lists logs, but the playbook has to be updated.
,
Nov 16 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/infra_internal/+/bc5c65aa30b54b169895f8319bc080623a64284b commit bc5c65aa30b54b169895f8319bc080623a64284b Author: Andrii Shyshkalov <tandrii@chromium.org> Date: Thu Nov 16 22:06:35 2017
,
Nov 16 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by hinoka@chromium.org
, Mar 10 2017