Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

Audit trail allows an administrator to keep track of user actions. The default implementation is based on Log4j 2 and the files used for logging can therefore be configured in any way you like. Magnolia also provides a Log Viewer tool, located in the Tools menu, to visualize these and other log files.


This feature is configured in two places, log4j2.xml file and in auditLogging configuration.


Here you define the loggers to be used by the audit logging. Here is an example extracted from the application log4j2.xml :

<RollingFile name="sync-log-audit"
   <PatternLayout pattern="%d{dd.MM.yyyy HH:mm:ss}%m%n"/>
    <SizeBasedTriggeringPolicy size="1MB"/>
  <DefaultRolloverStrategy max="5"/>
<Async name="log-audit">
  <AppenderRef ref="sync-log-audit"/>

auditLogging configuration

Define the actions you want to log in auditLogging configuration. You can enable the preconfigured actions and define which logger they should use. Define separators for each action or use the default separator (comma) for all of them.

Node name


































Below is an extract of the output of the logs. Format is: date, action performed, user ID, workspace, nodepath.

20.10.2008 11:59:33 , create , superuser , website , /untitled4

For actions move and copy it will add the original node path and the destination node path.

For actions login and logout the output differs. Date, user ID, action, and for login also the IP and the result of the action are logged:

21.10.2008 12:21:59, logout, anonymous
21.10.2008 12:22:05, login, superuser,, Success
  • No labels