[MAGNOLIA-1760] Review default log configuration Created: 10/Oct/07  Updated: 23/Jan/13  Resolved: 26/Jan/09

Status: Closed
Project: Magnolia
Component/s: build, core
Affects Version/s: None
Fix Version/s: 4.0

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-764 Add log/audit trail functionality Closed
supersession
is superseded by MAGNOLIA-2586 Cleanup default log configuration Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

We should review and simplify the default log4j configuration shipped with Magnolia. At the moment it logs in different files under MAGNOLIA_HOME/WEB-INF/logs, AND to catalina.out (or whatever container's default log file is), which is confusing. It seems people tend to look at the former when asked for logs, and those are mostly irrelevant in case of problems.

We should

  • simplify the configuration (I'd tend to use a single file)
  • provide (commented out or in a separate config file to be renamed) easy ways to get more logging for typical problematic cases

Also consider MAGNOLIA-18 and other log related issues.



 Comments   
Comment by Magnolia International [ 03/Apr/08 ]

Also to be taken into account: provide a minimal audit trail (who activated what, who deleted what, etc)

Comment by Magnolia International [ 31/Dec/08 ]

Modified the default pattern used for logging - the new one is imho much more readable. It does not provide all the debug info (source file name, method and location) anymore, which should make it much more performance

Providing commented-out typical "to-be-debugged" categories doesn't seem so important anymore - the log config tool works, and there are too many to keep it useful and clean.

While working on this issue, I'd like to understand why we need so many different files (appenders) and custom categories - I suspect the current configuration doesn't fulfill the actual use-cases.

Comment by Magnolia International [ 26/Jan/09 ]

Default pattern changed and cleaner. Further improvement at MAGNOLIA-2586.

Generated at Mon Feb 12 03:30:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.