Documentation Center

Logging more Experience Space events

By default, the only things that the Experience Space back-end logs to the Windows Event Viewer are internal errors and business rule validations; it does not log user input exceptions (unlike the Classic user interfaces, which do). If you want, you configure logging so that Experience Space logs user input exceptions as well.

Procedure

  1. On the Content Manager server, go to the config\ subfolder of %TRIDION_HOME%.
  2. Open the Content Manager configuration file, Tridion.ContentManager.config, for editing.
  3. To additionally log Experience Space user input exceptions, find the allEvents section and configure the log level to include informational messages by setting the switchValue attribute to All.
  4. Because this change greatly increases the amount of information being logged to the Windows Event Viewer, you may want to configure logging to log to a file instead. To do so, within the allEvents section, remove the line <add name="Tridion Event Log" /> in the listeners subsection, and replace it with the following line:
    <add name="Log File" />
    Events are now no longer logged to the Windows Event Viewer, but instead to the file specified as the log file; by default, the log file is the file Tridion.ContentManager.log in the log\ subfolder of %TRIDION_HOME%.
  5. Save and close Tridion.ContentManager.config.