Audit log with extra information

Avatar

Avatar

infinityskyline

Avatar

infinityskyline

infinityskyline

26-01-2021

My project has requirement to log all user activities.. i.e., what all is happening in the environment and by whom. I have enabled  audit logging feature in AEM by going to http://localhost:4502/system/console/slinglog -> change the log level of logs/audit.log to DEBUG.

 

This solves my purpose and logs all the user activities but it doesn't log what content changes has been made. For example, if value of a property is changed from "Hello World" to "Hello Earth" I want to log both old and new values, if not both at least the new value.

 

Is this possible? If not using audit log, can be done with custom logs or any workflows?

AEM audit console logs

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Sanket_Kumbharkhane

Avatar

Sanket_Kumbharkhane

Sanket_Kumbharkhane

27-01-2021

You can use an event listener to listen to all the activities on your website. Create a separate class and log all the activities in info mode. 

  1. NODE_ADDED
  2. NODE_MOVED
  3. NODE_REMOVED
  4. Event.PERSIST
  5. PROPERTY_ADDED
  6. PROPERTY_CHANGED
  7. PROPERTY_REMOVED

https://aem.redquark.org/2018/10/day-14-eventing-in-aem.html

 

and then register that class with a new log file name at

http://localhost:4502/system/console/slinglog

 

Note: Its better to add more restriction to listen to those events like

a. listen only for cq: page 

b. under a specific  parent folder

c. Strictly for Author

as per the requirement.

Answers (3)

Answers (3)

Avatar

Avatar

KiranVedantam1992

Avatar

KiranVedantam1992

KiranVedantam1992

27-01-2021

Hi @infinityskyline,

 

For logging all the user-level activities, you can write a filter and log them to a custom log. Related thread here.

 

If you need only the content level changes, you can write some listeners and can log the activities. Please find my blog for the annotations here.

 

Hope this helps!

 

Thanks,

Kiran Vedantam.

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

991

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

991

Correct Reply

1.0K
Jörg_Hoh
Employee

31-01-2021

As already stated, it's not useful to log all repository changes, because 1) you have to filter out the changes caused by system processes 2) no one will ever review these changes, 3) they slow down the system and 4) consume a lot of storage.

 

For what purpose do you need the audit log? What is the livecycle of these audit log data, how long do you want/need to keep them?

Avatar

Avatar

kiranparab

Avatar

kiranparab

kiranparab

27-01-2021

Hi,

 

You don't have to write any custom code for listeners instead you can go with ACS commons available feature Audit log serch

 

https://adobe-consulting-services.github.io/acs-aem-commons/features/audit-log-search/index.html

 

It will Trace all the Audit log depends on your Event Type like Page created, Page deleted, etc.. and provide the required information as needed till the date Audit log is available in instance. Purging for Audit log should not happen for that particular date.

 

kiranparab_0-1611754357284.png

 

 

Thanks,

Kiran Parab