Browse by Topic

Using Store Logs

What We'll Cover

Store Logs can be used to help identify and troubleshoot errors or issues with your store, and provide a history to determine when specific events take place.

Only 50 pages of the most recent store logs are recorded at any one time — anything earlier cannot be accessed. There are two kinds of logs: the System Log and the Staff Action Log. They can be found by going to Server SettingsStore Logs.

Store Logs screen showing tabs for System Log and Staff Action Log


System Log

The System Log tracks events that have taken place on your storefront, including orders, payment transactions, shipping quote requests, and newsletter sign-ups.

Example store logs

Each system log entry includes a summary describing the nature of the event, when it happened, its severity, the type, and which module reported the event. Click the + to expand a log entry for additional information from the reporting module. This data can be useful when trying to identify and troubleshoot errors or issues with your store.

Example of a log entry expanding and collapsing.

Filter events by severity and type using the drop-down list and clicking Search. Use the text field to search for any specific events or terms.

System logs severities and types


Staff Action Log

The Staff Action Log records general information about changes made in the control panel, including template file updates, product imports, and page edits. Each log entry lists the user, their IP address, the action, and the date and time it was performed.

Example staff action logs

The data recorded in the Staff Action Log is for general reference and doesn't include specifics about the event. For example, updating a category will trigger a Staff Action Log entry, but what aspect of the category was changed is not recorded.

Filter staff action events by User using the drop-down list and clicking Search.

Staff Action Logs

Was this article helpful?