By default, the Experience Space back-end logs only internal errors and business rule validations and does not log user input exceptions (unlike the Classic user interfaces, which do). You can, however, change how logging is configured so that Experience Space also logs user input exceptions.
Procedure
- On the Content Manager server machine, go to the following location: %TRIDION_HOME%openapi/service/bin
- Open NLog.config for editing in a plain-text or XML editor.
- Locate the
<logger> element and change the value of minlevel attribute to one of the following values:
| Log level | Description |
|---|
Trace | For tracing the program flow and performing the finest level of debugging–logs messages with the highest level of detail about the application's lowest-level activity. |
Debug | For normal debugging–logs fine-grained messages about low-level functionality being executed, intended to discover the source of a problem. |
Info | Logs information messages related to normal activity and user behavior, plus all warnings and errors. |
Warn | Logs warnings of unexpected events as well as all errors. |
Error | Logs all errors–both fatal events and non-fatal errors. |
Fatal | Logs only critical errors, that is, events that cause the system to go down. |
- Save and close NLog.config.