Hi Team,
Is there any functionality in AEM to allow users to track past user actions or past user changes on web content in the platform in author instance.
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
AEM Audit Log is a convenient way to check who modified what and when within AEM pages or assets.
ACS Commons provides an Audit Log Search tool which allows users to do an AEM Audit Log search and see what properties of a page (and enclosed components) have been altered.
Audit.log- This log file is used by Jackrabbit to log changes to the repository. By default this log file is set to level info. There is not much logging going on at this level because of which audit.log seems to be empty. If you set this log file to log level debug you will see log messages every time you make changes to the repository. For example if you add a component to a page, delete a page etc.
In summary, as everyone is suggesting there is not a complete solution to monitor the user activity but yes you can certainly take leads from Audit log otherwise you need to build something custom.
Hi,
There is no user action auditing.
We don't have user action auditing. But versioning which helps us to compare content that's been modified. May be enable versioning and during multiple publishes, You can compare the web content.
There are no detailed level auditing of user actions, You can use versioning for governance purpose.
AEM OOB provides audit logs [1] for events that qualify for audit logging.
ACS commons audit log search interface [2] can be used, which allows administrators to easily search the AEM Audit Log to determine what user modified content and when. This can be useful when diagnosing content issues, job results or unknown changes on a site.
[2] https://adobe-consulting-services.github.io/acs-aem-commons/features/audit-log-search/index.html
AEM Audit Log is a convenient way to check who modified what and when within AEM pages or assets.
ACS Commons provides an Audit Log Search tool which allows users to do an AEM Audit Log search and see what properties of a page (and enclosed components) have been altered.
Audit.log- This log file is used by Jackrabbit to log changes to the repository. By default this log file is set to level info. There is not much logging going on at this level because of which audit.log seems to be empty. If you set this log file to log level debug you will see log messages every time you make changes to the repository. For example if you add a component to a page, delete a page etc.
In summary, as everyone is suggesting there is not a complete solution to monitor the user activity but yes you can certainly take leads from Audit log otherwise you need to build something custom.