Filters on addtional logfiles not working

Just been trying the additional logs support added to run configurations in IDEA 7.0. What I'm seeing is the output in another tab next to console. But it isn't colour-coded nor do the Hide INFO, Hide WARNING work as I'd expect. Hide INFO hides everything.. even SEVERE messages. Hide WARNING, Hide SEVERE meanwhile don't do anything.

It appears the logfile display isn't parsing the log levels at all? What logging frameworks are supported here? I'm using java.util.logging which really should be supported by default. Tried both simplelogging and xml formatting (xml formatting is really horrible - appears as text with no special consideration?).

Meanwhile if I spilt the logs to both file and console, the console view works as expected i.e. SEVERE stackdumps appear coloured red -- there's no filtering on the console.

Also had a issue with the "skip content" option, seems with it active when I rerun the app ANY updates to the logfile get ignored. With it off things work. Which seems to be the exact opposite of it's intention? (I think my logging configuration simply overwrites the log on each run, so container logs would behave differently.)

Is this just me?

- Richard

Message was edited by:
Richard Osbaldeston

3 comments
Comment actions Permalink

Hello Richard,

Log files react on line's text (INFO, WARNING, ERROR by default). You have
custom text filter in order to process additional severities.

Highlighting is not supported.

Thank you

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Just been trying the additional logs support added to run
configurations in IDEA 7.0. What I'm seeing is the output in another
tab next to console. But it isn't colour-coded nor do the Hide INFO,
Hide WARNING work as I'd expect. Hide INFO hides everything.. even
SEVERE messages.

It appears the logfile display isn't parsing the log levels at all?
What logging frameworks are supported here? I'm using
java.util.logging which really should be supported by default. Tried
both simplelogging and xml formatting (xml formatting is really
horrible - appears as text with no special consideration?).

Meanwhile if I spilt the logs to both file and console, the console
view works as expected i.e. SEVERE stackdumps appear coloured red --
there's no filtering on the console.

Is this just me?

- Richard



0
Comment actions Permalink

Log files react on line's text (INFO, WARNING, ERROR by default). You have

custom text filter in order to process additional severities.

That will help explain some of what I'm seeing. My application dumps some INFO messages when the application starts. It seems toggling the INFO filter removes the whole log as it assumes everything else is part of the same INFO message?

Are there no aliases for the standard java.util.logging? their default levels for ERROR is SEVERE. Can't really see myself creating custom levels just for the IDEA filters. Guess thats pretty minor point though (why'd you want to turn off the errors). I'm not sure its filtering WARNING and INFO as I'd expect though, maybe the attached stackdumps are also causing confusion.

Re: the "skip content" problem, I think you're missing an option to clear/reset the log on every run. As my logs get overwritten by default (standalone app) if I turn off logging or change the log file IDEA is unaware the logfile isn't being used and displays the contents of the previous run as new information. Turning that option on, the display isn't updated when the logfile is overwritten on subsequent runs (which is why I'd turned it off).

BTW By editing my log and changing SEVERE to ERROR manually it was suddenly highlighted exactly like the console.

- Richard

0
Comment actions Permalink

It seems toggling the INFO filter removes the whole log as it assumes everything else is part of the same INFO message?


Pretty sure I'm correct about that as the remainder of my log was a mix of more INFOs and SEVEREs.

I often have a bunch of FINEs and FINESTs (mostly via the JDK when I'm debugging with a global Level.ALL - need to trace RMI loading, garbage collection and the like) Its a shame they can't be aliased to INFO as they'll currently get 'merged' into their preceding INFO or WARNING or override everything else.

0

Please sign in to leave a comment.