"inspector_websocke" messages dominate client logs |
||
Issue descriptionclient.X.DEBUG logs such as the one here: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/165673689-chromeos-test/chromeos6-row2-rack24-host18/debug/ have a large amount of inspector_websocket transactions (in this case, about 10,000 of 13,000 lines). Are these really useful? They make inspection of the rest of the log much harder.
,
Dec 27 2017
True, a reasonable first step would be to make those lines easier to filter out. But even so, this would add extra steps to the diagnostic flow. Also it would make it harder for someone working with only a browser and ssh (for instance on the gbus). It's hard to tell how useful the information is. I have never used it so I would give it zero value. But since it has been added, it was probably useful at least once. It would be good to hear from someone who has used it.
,
Dec 28
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by ayatane@chromium.org
, Dec 27 2017Labels: Hotlist-Fixit
Status: Available (was: Untriaged)