The Application Logs page is used to research application issues. The application log contains essential information, such as log date, type, source, sequence, message, and more. The application logs help Optimizely Support track and identify exactly when an error occurred in Configured Commerce.
There are five types of application logs, listed from lowest to highest importance.
- Debug
- Info
- Warn
- Error
- Fatal
This article explains how to view application logs and also describes how logging takes place in containerized sites specifically.
View application logs
- To access application logs in the Admin Console, go to Administration > Application Logs.
- You can do the following in the application logs:
- Use the filtering options or search to refine the list of logs.
- Select additional columns to display in the application log table.
- Click the View icon to view the details of a specific application log record.
- Download the application logs.
Application logs for containerized sites
Optimizely updated logging for containerized sites to flow through Elasticsearch, including integration job logs and debug logs. This offloads the database in Configured Commerce and improves overall performance. This update automatically captures all debug logs, making it easier to perform research quickly if a problem occurs. If you recently upgraded, you may notice that logs appear to be missing after the new logs point to the Elasticsearch log and no longer point to the database log. Logs will display again as new log entries are recorded. In addition, with this update, logs may take from 30 seconds to 1 minute to display in the Admin Console.
When displaying records, Elasticsearch can retrieve up to 10,000 records at one time for paged viewing. To view more logs, adjust the search parameters by using the Advanced Search function and set criteria for the search different from the defaults. Doing so will result in a different set of viewable data.
Please sign in to leave a comment.