Export saves issues and events to a file you choose, and Create Report writes a report that opens in your browser. Both buttons sit in the Log Center's title bar, in its windows and in Tools › Salesforce B2C Commerce › Log Center
Sandbox 01
version2
Files
Issues
Events
Anomalies
Monitor
Storage
Filters
Warn
Open Source
Mark Fixed
Move to Backlog
RefArch (3)
~/Projects/storefront
Export
Click Export and pick what to export, then the format, in Export Log Center Events. The save dialog, Save Log Center Export, suggests a name such as zzrx-001.dx.commercecloud.salesforce.com-issue-20261029-143412.html
| Scope | Exports |
|---|---|
| Selected issue | The issue selected on Issues |
| Selected event | The event selected on Events |
| Current filters | Every issue that matches the query bar |
| Selected log files | The events of the files checked on Files |
| All events | Everything stored for the instance |
| Format | Use it for |
|---|---|
| HTML | Reading and sharing. It opens in any browser, with no server |
| JSON | Scripts and other tools |
| Markdown | Tickets, pull requests and AI chats |
- The export runs in the background as Exporting Log Center events: Opening the log store, then Writing issue 120 of 342
- When it's saved, the Log Center export saved notification names the file and its issues, such as 342 issues, and offers Open, Open in Browser and Reveal in Finder (Show in Explorer on Windows)
- An export lists at most 50,000 issues, and the notification says how many were left out, such as 12 more issues were left out: an export lists at most 50,000
- When it can't be written, Log Center export failed says why
- Secrets in the log text, such as passwords, tokens, cookies and authorization headers, are masked in exports, reports and copies
To copy one issue or event instead of saving a file, use Copy as Markdown in its details, see Read an issue
Create Report
Click Create Report and pick a report in Create Log Center Report. It's written in the background as Creating Log Center report, saved in the project and opened in your browser. The Log Center report saved notification says … is open in the browser, and Log Center report not created says why it failed, see Troubleshooting
| Report | Covers |
|---|---|
| Events report | The events in the current filters |
| Errors report | The ERROR events in the current filters |
| Investigation report | What you captured while investigating |
| Anomalies report | The anomalies detected, see Anomalies |
Reports are saved as .intellij-sfcc/logs-streaming/reports/<host>-<report>-<date>-<time>.html in the project, so you can keep or share them. Each one has these sections:
| Section | Shows |
|---|---|
| What happened | The key numbers and a recommended next action |
| When events occurred | A chart of the events over the range |
| Largest event patterns | The issues with the most events, with their level and source |
| Investigation progress, Findings & actions | What is checked so far and what to do next |
| Anomalies | The anomalies of the period, most severe first |
| Technical evidence | The original messages, excerpts and stack traces |
Create Errors Report File in Tools › Salesforce B2C Commerce › Log Center writes the errors report of everything stored, with no filters, and opens it in the browser
Troubleshooting
| Symptom | What to do |
|---|---|
| The level filter leaves out ERROR | Add the Error level or clear the level filter, then create the errors report again |
| Reports are saved in the project folder, and this project has none | Open a project folder, such as your cartridges' repository |
| No logs are stored for this instance yet | Parse a file first, see Files & Tails |
| A scope is missing from Export | Select a row on Issues, Events or Files first |