[Feature]: Add console log filtering by levels

[edrennikov]

🚀 Feature Request

Add CLI parameter --console-log-levels=<levels...> to restrict console logs output to client.

List of possible levels (taken from ConsoleMessage.type() return type):

  log,
  debug,
  info,
  error,
  warning,
  dir,
  dirxml,
  table,
  trace,
  clear,
  startGroup,
  startGroupCollapsed,
  endGroup,
  assert,
  profile,
  profileEnd

One special "level" is none to disable all levels.

Example

• --console-log-levels=warning,error enables only warning and error logs.
• --console-log-levels=none disables all console logs.
• If option is not set, then all logs are enabled by default.

Motivation

This could be helpful in cases if web page is too verbose in console and this consumes a lot of tokens of LLM.

[dgozman]

I assume we'd need better flexibility than just console levels. Perhaps some kind of a regex filter, or similar. See also #1237.

[edrennikov]

Do you mean regex filter by log message, not type, right?
Then we can have two options:

• --console-log-levels <levels...> — to filter by levels
• --console-log-filter-regex <regex> — to filter by message content

[edrennikov]

This microsoft/playwright#38439 PR introduces similar, but different functionality: e.g. if --console-level info is set, then error logs will also be passed. But here I want to introduce different functionality: e.g. I want to block error, but show info. Because there could be many errors on site which I don't need, but my own code could log some info level logs which I want to see. Also I want an option to completely disable logs.

[edrennikov]

@pavelfeldman PR microsoft/playwright#38439 does not solve the issue which is described here. It does not allow to fully control which logs will be returned to the client. I would consider these features to be different. And would like to reopen this one.