Log File Editor

Analyze SFCC .log files with parsed entries, filters, a timeline, stack traces, and source navigation in VS Code.

The Intellij SFCC Log File Editor turns an SFCC .log file into a searchable view of parsed entries. Filter a large file, inspect a request's context, and follow stack traces into matching workspace code while keeping the raw log available.

Open a log

Open a .log file in VS Code. If it opens as plain text, use Reopen Editor With... and choose Intellij SFCC Log File Editor. The custom editor works with log files; use Log Streaming to follow remote sandbox output as it arrives.

Narrow the investigation

Start with the time window around the failing request, then narrow by severity or a search query. Depending on the fields present in the log, filters can also target categories, request IDs, sites, endpoints, sessions, source paths, and stack traces.

The histogram helps locate bursts of activity. Select an entry to inspect its complete message and context. Filters can only match information present in the file; an entry without a request ID or stack trace cannot supply that missing context.

Follow stack traces into code

Use a source link from a stack frame to open the matching workspace file. Resolution depends on the local cartridges and available source information. Keep your workspace aligned with the sandbox code version when investigating an error.

If a frame cannot resolve, inspect the raw location and search the workspace. For TypeScript projects, see TypeScript debugging to understand the mapping between deployed JavaScript and local TypeScript.

Return to raw text

Use the editor's raw view when you need the original formatting or an entry does not parse as expected. Raw navigation can take you to the corresponding log line, so you can compare the structured entry with its source.

Share an investigation

Use the editor's copy and export actions to take filtered results or an error report into a ticket. The extension applies redaction to supported shared text and structured payloads. Review the output before sharing it outside your team, since free-form log messages can contain application-specific data.

  • Log Center: group recurring errors and investigate related occurrences.
  • Log Streaming: follow remote sandbox logs.
  • SFCC MCP: use supported log investigation tools with a compatible AI client and configured permissions.

On this page