Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347120 - Loglevel in log pattern
Summary: Loglevel in log pattern
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: 3.0.0.M03   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.0.0.M05   Edit
Assignee: Glyn Normington CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 05:07 EDT by Jean-Pierre Bergamin CLA
Modified: 2011-05-25 09:46 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Pierre Bergamin CLA 2011-05-25 05:07:02 EDT 
Build Identifier: 

The first thing I always do when installing virgo is changing the log pattern in the serviceability.xml to output the loglevel. I think the log level is a viable information that should always be output.

I'd suggest to change the log patterns of the preconfigured serviceability.xml file to:
<Pattern>[%d{yyyy-MM-dd HH:mm:ss.SSS}] %-5level %-28.28thread ....</Pattern>

Reproducible: Always
Comment 1 Glyn Normington CLA 2011-05-25 08:46:04 EDT 
Actually I've wanted to see the log level in the past, but always put up with not having it, so I'll take a quick look at this and slip it in if appropriate.
Comment 2 Glyn Normington CLA 2011-05-25 08:59:52 EDT 
Changed the pattern to include the log level for "trace" logging but not for event logging as event log entries already include a message number ending with a character denoting the log level.

Pushed kernel commit 30339d3848c42be52196f53955177e083908dde2
Comment 3 Jean-Pierre Bergamin CLA 2011-05-25 09:45:18 EDT 
Whow. That was fast. :-)
Thanks.
Comment 4 Glyn Normington CLA 2011-05-25 09:46:34 EDT 
You're welcome. Thanks again for raising this.