Log Streaming
WebDAV-backed SFCC sandbox log access in JetBrains IDEs
Use the JetBrains plugin to inspect sandbox logs from the same connection you use for upload, deployment, and remote file operations. JetBrains exposes logs through the B2C Explorer connection tree and browser actions, while Log Center remains a VS Code and SFCC LSP feature.
Open Logs
Select a Connection
Open B2C Explorer and select the sandbox connection or connection group you want to inspect.
Open Logs in Browser
Right-click the connection and choose Open Logs in Browser. The plugin opens the sandbox WebDAV logs URL for the selected connection.
Browse Log Folders
Expand Log Files or Security Log Files in the Explorer tree to browse available log files directly from the IDE.
Log Sources
Log Files maps to the sandbox /Sites/Logs WebDAV folder. Use it for development logs such as custom error, custom debug, warn, job, and system output generated by the active sandbox.
Security Log Files maps to the sandbox /Sites/Securitylogs WebDAV folder. Use it when you need authentication, authorization, or platform security events exposed by the sandbox.
File Actions
When a .log file is selected in B2C Explorer, the plugin exposes the same remote-file actions used elsewhere in the Explorer:
- Download and Open - download the selected log file and open it in the IDE editor
- Open in Browser - open the remote log file in the browser
- Copy Remote Path - copy the exact WebDAV path for sharing or troubleshooting
- Clear log file - clear one or more selected
.logfiles when the remote path is allowed - Refresh - reload the folder contents after new log files are created
How It Differs From Log Center
JetBrains log access is focused on browsing and managing sandbox log files through WebDAV and browser links. VS Code Log Center adds parsed issue workflows, source-context search, diagnostics, and fix tracking through the VS Code extension and SFCC language server.
Use the JetBrains workflow when you want quick access to remote log files from the IDE. Use VS Code Log Center when you need parsed issue triage and the LSP-backed fix loop.