[MAGNOLIA-5630] Audit logging logs only on log level ALL Created: 17/Jan/14  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.2.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Frank Sommer Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Visible to:
Rainer Blumenthal

 Description   

Audit logging logs only on log level ALL, but ALL should not the default log level in a production logging configuration.
Additional there is used a custom log level for audit logging (AUDIT_TRAIL). This custom audit log level makes no sense. It has the priority 99, but TRACE has already the priority 5000. In my opinion the only case which makes sense would be that the custom log level has a priority > 50000. Then the audit logging doesn't depends on log4j.xml.



 Comments   
Comment by Jan Haderka [ 31/Mar/14 ]

Hi Frank,

the audit log should always go to separate file so it contains only audited content and doesn't get mixed with any other content. Because of that, the prio level should never cause any troubles.
Can you please try to explain the use case for mixing those with any other logs?

Thanks,
Jan

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:06:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.