[MAGNOLIA-764] Add log/audit trail functionality Created: 08/Mar/06  Updated: 23/Jan/13  Resolved: 23/Oct/08

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

Type: New Feature Priority: Major
Reporter: Tom Wespi Assignee: Teresa Miyar
Resolution: Fixed Votes: 2
Labels: businesscritical
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MAGNOLIA-301 Monitoring: author activity, ... Closed
relation
is related to MAGNOLIA-1760 Review default log configuration Closed
supersession
supersedes MGNLEE-117 Accesses not registered for ldap users Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

log with username, ip and time:

  • delete content
  • rename content
  • deactiviate content
  • activate content
  • change content


 Comments   
Comment by Stojan Peshov [ 08/Mar/06 ]

Do you mean log as log4j ?
I want to make some sort of logger but to keep all the entries in jcr
in that way it can be easily made Recent Changes functionality with links (wiki alike)
anyway
I was wondering what's the easiest way to catch the changes?
I could use interceptor for delete and move...
and maybe Save class for some changed nodeData's
what about create and activate ?

Comment by Tom Wespi [ 10/Mar/06 ]

yes, log4j

but entries as text file, not in the repository, because sometimes repositories break...

Comment by Philipp Bracher [ 10/Mar/06 ]

A log4j JCRAppender would be nice. This makes it configurable.

Comment by Boris Kraft [ 22/Aug/06 ]

Basically, any action should be logged to an audit trail. This issue is critical because for service providers. Unless there is an audit trail that proves who did what when, its always (by default) their or Magnolia's fault if something goes wrong. A user accidentally deletes a site tree? Do you think he will tell his boss? Or was its Magnolias fault? You get the idea ...

Comment by Nicolas Modrzyk [ 23/Aug/06 ]

I am doing something similar in irbridge using aspects. is that of any interest ? Does that need to be discussed at the meeting next month ?
The great thing with aspects, is that the logging is transversal so it's not cluttering the code at all.

Comment by Sameer Charles [ 12/Oct/06 ]

We decided to use Aspects for next version until we use spring.
It would be great if Nicolas can help up understanding his setup, we can work together on this.

Regarding storage of this information, It does not make any sence to have static text files.
If we have all logged data in JCR, properly structures or unstructured we are free to do whatever with that, you can export it as logs in any format
/ create reports etc and its not limited in its output.

I propose to have a seperate workspace "auditlog" to start with.

Comment by Magnolia International [ 31/Jan/07 ]

@Stojan Peshov : what you're looking for can be achieved with the versionning functionalities of jcr

Comment by sebastian.frick [ 01/Feb/07 ]

@gregory: so in which way is it possible to find out more details of an delete action via jcr?

Comment by Magnolia International [ 01/Feb/07 ]

Node.getVersionHistory()?

Comment by Jan Haderka [ 04/Sep/08 ]

While this is certainly important new feature, it is not system critical (i.e. doesn't cause loss of data or system crash as per definition of critical issue).

Comment by Teresa Miyar [ 22/Oct/08 ]

Documentation will be available on http://documentation.magnolia-cms.com/administration.html

Comment by Philipp Bracher [ 23/Oct/08 ]

use lower case for /server/AuditTrail node as we do every where else: /server/auditTrail

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