Enabling trace logging
You can enable trace logs for different features within IBM OpenPages® with Watson™ to help diagnose issues that you might run into.
About this task
Trace logging generates a large amount of data on the application server. Enable trace logging only during testing and when other users are not on the system. Make sure to disable trace logging before users access the server again.
When trace logging is enabled, separate log files are created in the <OP_HOME>/aurora/logs/debug directory. These log files have a suffix that indicates the log type, for example <server_name>-workflow.log, <server_name>-sdk.log, and so on.
Generally, trace logs contain the following information:
- Enter and exit messages for relevant API calls
- Timings for each method
- Targeted debug logging
The following trace logs are available:
- Trigger Logger – Logs trigger evaluations and executions.
- Workflow Logger – Logs all workflow API calls and action evaluations.
- Calculation Logger – Logs all calculations.
- Cognos® Integration Logger – Logs computed fields, reporting fragments, and connections to Cognos Analytics from OpenPages.
- SDK Logger – Logs all SDK API calls.
- Cache Logger – Logs cache loading at startup and logs updates that occur over time.
- Persistence Logger – Logs database access.
- Custom REST Logger – Logs access to custom rest endpoints.
In 8.2.0.1 and later, you can also use the Login Logger to log all single sign-on authentication events. The log file is named <OP_HOME>/aurora/logs/debug/<server_name>-auth.log.