Bugzilla – Full Text Bug Listing
| Summary: | Loglevel in log pattern | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Jean-Pierre Bergamin <james> |
| Component: | unknown | Assignee: | Glyn Normington <glyn.normington> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | glyn.normington |
| Version: | 3.0.0.M03 | ||
| Target Milestone: | 3.0.0.M05 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
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. 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 Whow. That was fast. :-) Thanks. You're welcome. Thanks again for raising this. |
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