Filter console messages!

[Varunkumar Nagarajan]

Hi,

In one of my applications, third party libraries are polluting the console with so many log messages. It is getting increasingly difficult for me to look out for my messages in that stream. I am looking for ways to have better control over the console panel. 

Filters

I am looking for a way to filter console messages. Currently, there is an option to search for the messages but not filter. Ability to set inclusion / exclusion filter patterns would be really useful. 

Tags

Console.group is a nice way to group the log messages. But, we can have only one group open and write logs only to the currently opened group. It would be handy if we can provide a TAG (like Android logs) and the messages with same TAGs are grouped together. 

Is there any alternative for this in CDT? Thoughts? 

Thanks,

Varun

[Sam Dutton]

+1

[Paul Irish]

You can already filter console.log/warn/error independently.  I attached an animated gif to explain. (You can even hold cmd to select multiple).

Meanwhile, I have heard discussions around adding a "Filter" checkbox to the console's search, much like on other tabs.

[Varunkumar Nagarajan]

I am aware of the filters on log level but that wouldn't be very helpful in my case. Almost all the libraries use console.log() only. 

Filters (like in other tabs) would be a good start but the ability to filter based inclusion / exclusion patterns would be really useful given that console panel is becoming more verbose when compared to other panels. 

Varun

[br...@imanen.com]

+1 on the tag idea.

[maxka...@gmail.com]

http://gramki.wordpress.com/2011/05/08/google-chrome-console-message-filtering-through-tags/

+1

[grigo...@gmail.com]

+1 on filters. 412 for ajax requests is success, but it effectively kills console spamming dozens of messages per second :(.

[Kurt Flint]

Huge +1 on filters. I'm sick to death of hunting through the log output from crappy plugins looking for my own messages.

[Vsevolod Vlasov]

It is also possible to filter messages from certain URL using console context menu->filter currently.

On Tue, Jun 25, 2013 at 10:29 AM, Kurt Flint <ku...@monkeykeyboard.com> wrote:

Huge +1 on filters. I'm sick to death of hunting through the log output from crappy plugins looking for my own messages.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Kurt Flint]

I do, and I also have had some success over-riding console.log. 

But my best success to date has just been to throw warnings. And I really am amazed how many problems people are happy to ship their plugins with. No pride in a lot of these people.

   -- Now featuring more MONKEY POWER

                @monkeyKeyboard.com

Kurt Flint

ku...@monkeykeyboard.com

(831) 854 - 7245

[Paul Irish]

Alright, let me give a summary of what's now available 

Filtering by file:

Filtering by message category:

Filtering by message severity:

(cmd-click for multiple)

and this just landed yesterday..

Filtering console messages by string/regex

https://code.google.com/p/chromium/issues/detail?id=174795

Just landed yesterday so you'll start seeing it in Canary soon. :)

I think this last one solves most of the use cases brought up here. 

Some of these are available in stable but Canary has the latest, of course.

[Kurt Flint]

The sstring/regex does exclusion? Awesome! 

How many months before this hits stable, which I am working with? It would be cool if there was a channel with a "developer stable" - something almost identical to what your users are using, except with at least the Canary debugging toys added on. And nothing else! One thing I like about Firebug is that as a plugin with extensions you can pick your platform, and pick your poison when it comes to chasing down a reported issue or developing in a particular environment.

Cheers!

By the way, can you describe where exactly your mouse pointer was for the first three clicks? I'm probably guessing correctly, but I'm in "away with a tablet" mode today. Your screen capture doesn't capture your pointer.

Kurt​

[Dmitry Zvorygin]

Paul is running ahead a little with his hand-made "screenshot" of console filtering :-)

Current version doesn't support regex, and shows only log messages containing passed string. So it might be useful, for example, to see all messages containing your library specific tag for example.

Is regex is really needed for filtration? If yes - it's surely not very hard to add it.

WBR,

Dmitry.

[Paul Irish]

Thanks for the catch Dmitry.. (yes my last mock was photoshopped. :)

I don't think regex is particularly needed for console filtering. I can see better usecases for excluding search matches.

[John J Barton]

As in Paul's screenshots, I noticed in using recent builds that the Filter By Message Category seems remove CSS by default. I was surprised by this. It may be a great choice for many users who know about the Filter, but those who don't notice it (most?) will simply think the devtools are failing to list CSS warnings all of sudden. 

Unless that is also a photoshop ;-)

jjb

[Paul Irish]

I believe it was disabled by default because on nearly all production sites it floods the console with warnings about IE hacks that are present in the CSS.

But Alexander has addressed many of those and now the flooding may be quiet enough. It's a tough call on if it should be default and will require some more testing to see what syntactically illegal things are somewhat legit.

[Dmitry Zvorygin]

Yes, Paul was right, CSS is intentionally hidden by default.

When CSS warnings was landed first time, before "Filter By Category" patch, there were complains about flooding console, so that CSS warnings were temporarily disabled until "Filter patch" was landed.

I'm currently working on patch showing aggregated info on top of console like "100 messages are filtered out and not shown" and button to quickly reset all the filters - that will help users new to filters.

[Paul Irish]

Nice! :)

And here are the real screenshots of the new console filters:

[cast...@gmail.com]

+1 of "Filtering by file" idea. I think this will resolve issues with extensions, that log something into console. But I want to log all messages from particular file, not only console.log/warn/error etc. For ex. I like to have informations about XHR, but drives me crazy when extension ( https://chrome.google.com/webstore/detail/instant-translate/ihmgiclibbndffejedjimfjmfoabpcke ) print me something like this 

With optimism,

Krzysztof

[Dmitry Zvorygin]

Hi, Krzysztof

Have you read all the thread?

Currently you already have ability to filter out all "spamming" message source, by rught-clicking on them, as Vsevolod proposed.

WBR,

Dmitry.

--

[cast...@gmail.com]

Hi Dmitry,

I have Canary 30.0.1553.3 and didn't find place, where I can filter certain URL or file. I've clicked RMB on URL or file name, but no luck. Where should I click to filter it? Note that these are XHR logs from installed extension.

Thanks,

Krzysztof

W dniu sobota, 12 stycznia 2013 14:15:52 UTC+1 użytkownik Varunkumar Nagarajan napisał:

[Vsevolod Vlasov]

You should right click on the message itself, not on the link.

It doesn't work for XHR logs though indeed, can you file a bug on crbug.com and send a link here?

Thank you,

--

[cast...@gmail.com]

Bug solved, Dmitry Zvorygin helped me.

Simply, I use mac and context menu is not working on mac ;) There is a bug to fix already attached to Dmitry.

Thanks,

Krzysztof

W dniu sobota, 12 stycznia 2013 14:15:52 UTC+1 użytkownik Varunkumar Nagarajan napisał: