JEP 158

[Jesper Wilhelmsson]

Hi Kirk,

To select what should be logged there should be logging modules. A module could 
be for example class loading, gc, jit compiler etc. The logging level is just a 
way to control how much logging you want. Setting gc=info would give you some 
basic gc logging while gc=debug would give you more detailed info.

A typical command line could look like

|
-Xverbose:gc=debug,finalizer=info,compiler,alloc,cookies=trace|

/Jesper


On 2012-06-19 23:44, Kirk Pepperdine wrote:
> Hi,
>
> I see the logging framework JEP finally was published. This is great news.
>
> I'd like to comment on this quality
>
> "Logging is performed at different levels: error, warning, info, debug, trace"
>
> If we accept the problems associated with level based logging, these name 
> work for generic frameworks such as Log4J and JDK logging. However, the names 
> are meaningless in that they carry no semantic context with what would be 
> logged. The nice thing about the current set of flags is they convey the 
> information that will be printed.
>
> On the question of log levels. I was hoping that we would have learned from 
> the follies of using level based logging instead of a digital or tag based 
> system. IOWs a on or off different aspects without having to eat the whole 
> elephant of records that some developer arbitrarily decided should be dumped 
> at a particular log level. One can level tags.. but you can't get tags or 
> digital behaviour from levels.
>
> Kind regards,
> Kirk Pepperdine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20120620/984f83e4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jesper_wilhelmsson.vcf
Type: text/x-vcard
Size: 251 bytes
Desc: not available
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20120620/984f83e4/jesper_wilhelmsson.vcf>