New issue
Advanced search Search tips

Issue 797770 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

"inspector_websocke" messages dominate client logs

Project Member Reported by semenzato@chromium.org, Dec 27 2017

Issue description

client.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.

 
Cc: akes...@chromium.org
Labels: Hotlist-Fixit
Status: Available (was: Untriaged)
Use grep or sed to filter out those lines (which would be a lot easier if we could keep all log messages on a single line, I would file a separate bug for that).

I think these logs could be useful for debugging, but in most cases is probably noise; we should decide on a more concrete logging policy to guide these kinds of decisions.
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.
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 28

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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