The Intellij SFCC Log File Editor turns an SFCC .log file into a table of unique events. It indexes the file once, groups repeated messages, and lets you filter, inspect, and copy events while the raw text stays one click away
Open a log
The editor is registered for .log files as an optional editor, so a log you open from the Explorer still opens as text. Open it in the Log File Editor in one of these ways:
- Open in Log File Editor in the editor title bar of a
.logfile - Reopen Editor With... in the Command Palette, then Intellij SFCC Log File Editor
- Download a
.logfile from the WebDAV Explorer or from Log Center. Downloaded logs open in the Log File Editor directly, unless you download them to a folder of your choice
The first time a file opens, the editor reads it in small chunks and builds an index, with the progress, the lines parsed, and the read speed on screen. The index lets you search and jump through large files without loading the whole file into memory
The editor header
| Action | What it does |
|---|---|
| Parse | Sends the file's events to the global Log Center. Once it is done, the header shows In Log Center and the button becomes Reparse, which sends the whole file again. Log Center keeps only new, unique events |
| Tail | For a downloaded WebDAV log that still exists on the instance, appends new records to the downloaded file and streams them into this editor. Stop tailing ends it, and the next tail resumes from the last downloaded byte. Local logs can be parsed but not tailed |
| JSON | Copies the current rows as JSON |
| Log Center | Opens Log Center |
| Raw | Reopens the file in the text editor |
The same Parse, Log Center, and Raw actions, plus Focus Log Filter, sit in the editor title bar. The file info icon next to the file name shows whether it is a Downloaded log or a Local log, SFCC-compatible log detected or Plain text log - no SFCC header, and its size, raw lines, format, instance, path, and origin
Pick the instance
Parsed events always belong to an instance. A downloaded log whose hostname matches a connection, or a local log you already parsed, goes straight to its connection. Otherwise Select instance for local log, or Select instance for downloaded log with the hostname, asks which connection it belongs to: Parsed records will be written to the selected instance database. Log Center switches to that instance
Filter the events
The table lists unique events, so a message that repeats shows once with its count. Columns are Type, Count, Latest, Message, Source, Stack, and Line, and each column header sorts the table
Type in Filter text, stack traces, source paths... to filter by text. The arrows next to the field step through the matches, and the counter shows the current match. The Filters panel narrows further, with controls for the fields present in the log:
| Group | Filters |
|---|---|
| Event | Level, category, and time range, from Last 15 min to Last 24h |
| Context | Sites, endpoints, sessions, source files, and a request id |
| Trace | Stack status, such as With stack, Resolved, or Unresolved, and whether the source is mapped |
Each active filter shows as a chip under Active, and Clear all removes every filter. Three charts follow the current filters:
- Messages over time. Use its range buttons, a custom range with Apply, or drag across the chart to narrow the time window. Reset returns to the whole file
- Severity, the occurrences per level
- Source files, the files that logged the most events
Drag a column edge to resize it, or focus the edge and use the arrow keys. Widths are remembered
Filters only match what the file contains. An entry without a request id or a stack trace has nothing to match for those filters
Inspect an event
Select a row to open its details beside the table. The drawer shows the level, the occurrence count, the site, and the line, then these sections:
- Occurrence summary, with the sessions of the event. Click an ID to filter the table by that session
- Resolved code targets, the routes and hooks the event maps to
- Grouped occurrence data, the request contexts of every occurrence
- Quick filters, the message, the stack trace, source locations, nearby lines, and the raw line
- Header metadata, when it adds more than the message, and the parsed JSON
Find in all detail sections searches all of them at once. Message, metadata, and JSON sections open Full screen. Esc closes an open filter menu, then the drawer
Stack frames that resolve to your linked cartridges or global modules carry a source link. Click it to open the file at that line, or turn on Linked code only to show only those frames. Keep your workspace on the same code as the instance, so the lines match. For TypeScript cartridges, see Debug TypeScript on a Sandbox
Copy and share
The drawer groups its actions:
| Group | Actions |
|---|---|
| View | Collapse all or Expand all detail sections |
| Copy | Message, or Message + stack |
| Share | For chat, the full issue formatted for a chat or a ticket |
| Data | Raw line, parsed JSON, or Open raw to jump to the line in the text editor |
Copied text is redacted: authorization and cookie headers, bearer and basic tokens, and the values of sensitive fields such as tokens, secrets, and keys are replaced with <redacted>, in plain text and in JSON. Free-form messages can still contain application data, so review the text before you share it outside your team
Access
The Log File Editor needs Intellij SFCC access through a trial, a personal subscription, or an organization seat. Without it, the editor shows Intellij SFCC access required with the button for your next step (Sign In, Choose a Plan, Renew Subscription or View Assigned Seat, and Open Dashboard when access could not be checked), Sync Access once you are signed in, and Open raw text