Everything Log Center collects stays on your machine, in a local database per instance. From there you can export it as a report for a ticket, a teammate, or an AI agent, read the totals on the Overview tab, tune how hard Log Center works, and clear the data when you are done
Export
Export in the Log Center header picks a format and a scope:
| Format | What you get |
|---|---|
| Generate report… | A report you can attach to a ticket, as HTML and PDF. See Generate a report |
| HTML | An interactive triage page plus an errors CSV and a README for QA and agents |
| JSON | The events as JSON, with sensitive values redacted |
| Scope | Includes |
|---|---|
| Current filters | The events that match the Events tab right now |
| Fixed events | The events marked fixed |
| Full export | Every event of the instance |
The HTML export writes a folder in your project, .intellij-sfcc/logs-streaming/reports/<date>/<n>/, with these files:
| File | Contents |
|---|---|
report.html | The interactive triage page, with the same filters and event details as Log Center |
report-errors.csv | One row per error event, for a spreadsheet or a tracker |
workflow.svg | The visual guide shown in the README |
README.md | How to read the report, for people and AI agents |
When it is done, Interactive Logs HTML report exported with report-errors.csv and README.md. offers Reveal in File Explorer and Copy Path. The JSON export confirms Logs JSON report exported. with Reveal in File Explorer and Open in VS Code
The drawer of an event has its own Export for the selected event or occurrence
Generate a report
Generate report… opens a dialog that captures a fixed scope as an offline attachment:
Pick the project
Save to project chooses the workspace folder. The report goes to .intellij-sfcc/logs-streaming/reports there, and the choice does not change the instance or events being analyzed
Pick the report
Events in selected scope, ERROR level in selected scope, Detected anomalies, or Captured investigation
Pick the formats
HTML, PDF, or both, then Generate. Cancel generation stops it and keeps the formats already finished
The result offers Open PDF, Open HTML, Folder, Jira summary (copies a short summary for a ticket), and Path. If a format fails, Retry unfinished formats runs it again. The folder also holds jira-summary.md, report-errors.csv, a README.md, and a manifest.json with checksums. Both formats open offline, without the extension
Report… in Anomalies opens the same dialog for the detected anomalies
Generate Error Report
Generate Error Report in the Command Palette writes a Markdown report of every event, titled 🪵 Intellij SFCC Logs Report, and opens its preview. It has a summary table, a severity breakdown, the top source files, and a section per event with its code reference, original log line, and stack trace
Overview
The Overview tab of the full panel shows the instance at a glance:
- Messages parsed, Log files known, Database size, and Error events
- Messages over time for every parsed event
- Database, with Open DB and Open downloads
- File states, Log categories, Top source files, and Top event groups
The local database
Log Center keeps one SQLite database per instance, with full-text search, in VS Code's storage for the extension. Downloaded log files are stored next to it, in a folder per hostname. Parsed events, fixed and backlog marks, and parse progress survive a restart
- Hover the database size in the header for Local SQLite database, with Open database location
- When you switch to an instance with many events, Loading Sandbox 01 events… 42% shows while it loads
- Remote files on the instance are never changed by Log Center
Clear data
Clear data removes local data of the active instance. Each action asks for a VS Code confirmation first:
| Action | Confirmation | Removes |
|---|---|---|
| Clear all local data | Clear all Logs Manager local data? | The database and the downloaded log files |
| Clear local database | Clear the Log Center database? | Parsed events, indexes, diagnostics, and tracked rows. Downloaded files stay |
| Clear downloaded log files | Delete downloaded log files? | The downloaded .log files. Parsed data stays |
Under Export or inspect first, the menu also links Export report, Database folder, and Downloaded logs. Remote WebDAV files and log files you own outside Log Center's storage are never deleted. To empty a log file on the instance, use Clear Log File
Settings
The Settings tab tunes Log Center. Number values are saved to your VS Code settings under intellij-sfcc.logs, and Open in VS Code Settings jumps there
| Group | Row | Setting |
|---|---|---|
| Filter menus | Infinite-scroll batch | intellij-sfcc.logs.filterOptionBatchSize |
| Filter menus | Maximum filter values | intellij-sfcc.logs.maxFacetValues |
| Remote file list | Auto-refresh interval | intellij-sfcc.logs.autoRefreshIntervalSec |
| Remote file list | Auto refresh | Saved with this view, not in VS Code settings |
| Parsing & tailing | Worker concurrency | intellij-sfcc.logs.parseConcurrency |
| Parsing & tailing | Initial parse concurrency | intellij-sfcc.logs.initialParseConcurrency |
| Parsing & tailing | Range chunk size | intellij-sfcc.logs.rangeChunkSizeMb |
| Parsing & tailing | Tail polling interval | intellij-sfcc.logs.tailIntervalMs |
| Search index & memory | Indexed occurrences | intellij-sfcc.logs.maxIndexedOccurrences |
| Search index & memory | Raw examples | intellij-sfcc.logs.maxRawExamples |
See the defaults and ranges in Settings