The Log Center reads the logs of your instances into a store on your machine, one tab per instance. Repeated errors become one issue each, so you search, filter and fix them without downloading files
Sandbox 01
version2
Files
Issues
Events
Anomalies
Monitor
Storage
Parse
Tail
Parse New Data (3)
RefArch (3)
~/Projects/storefront
Search & Filters
Search Log Center issues and events with wildcards, filter them with pills and the filter popup, narrow the time range and zoom the event timeline
Files & Tails
Parse instance log files and archives into the Log Center, tail them for new lines, follow the work in Monitor and manage the stored logs in Storage
Logs in the Editor
Read SFCC logs in the editor with level colours, folds, links to your code, quick documentation and structure, and in the Log Center's log viewer
Issues & Anomalies
Read each Log Center issue with its stack and code, mark fixes, keep a backlog, catch spikes and new errors, and see log errors in the editor gutter
Status Bar & Gutter
The Log Center widget in the IDE status bar, the log error marks in the editor gutter, and how the paths and routes in logs map to your project
Export & Reports
Export Log Center issues and events as HTML, JSON or Markdown, and write events, errors, investigation or anomalies reports that open in a browser
Open it
The Log Center button sits low on the left bar, after B2C ODS. It appears in projects with SFCC code, like B2C Credentials, see Projects without SFCC code
| From | How |
|---|---|
| The tool window bar | Click Log Center |
| The main toolbar | More › Log Center |
| The Tools menu | Tools › Salesforce B2C Commerce › Log Center › Open Log Center or Open Instance… |
| B2C Explorer | Right-click a file under Log Files and choose Open in Log Center or Tail in Log Center, see From B2C Explorer |
| A log open in the editor | Open in Log Center on the banner above the log, see Logs in the Editor |
| The status bar | Click the Log Center widget, see Status bar |
Tools menu
Tools › Salesforce B2C Commerce › Log Center holds every Log Center action. Find Action finds them too
| Action | What it does |
|---|---|
| Open Log Center | Opens the issues, events and files of the active instance |
| Open Instance… | Opens an instance's logs in a new tab, see Instance tabs |
| Open in Editor Tab | Opens the Log Center in an editor tab with the current filters |
| Open in New Window | Opens the instance in a window of its own, one per instance |
| Stop All Log Tails | Stops every Log Center tail in this IDE |
| Export, Create Report | See Export & Reports |
| Create Errors Report File | Writes the errors report of the stored logs and opens it in the browser |
| Manage Stored Logs… | Lists, opens and deletes the stored logs of each instance, see Storage |
| Show Stored Logs Location | Opens the instance's store folder in the system file manager |
| Delete Stored Logs… | Deletes the instance's stored logs and closes its tabs |
| Copy Agent Fix Workflow | See Fix with an AI agent |
| Log Center Settings | Opens Settings |
Instance tabs
Each instance gets its own tab, named after its connection and coloured by kind: red for production, blue for staging, green for development. Tabs come back when you open the project again, and their tails resume
The selected tab opens into its instance's header, the row of views under it. Tab and header share the kind's light colour, so they read as one surface, and the selected view is underlined in the kind's colour. An instance of another kind, such as a sandbox, takes a light wash of the theme's focus colour. Tabs not selected keep a faint border in their colour. When the tabs don't fit, they shrink, then the rest go into All Tabs behind a chevron. The selected tab always shows
Resting the pointer on a tab shows the instance's card: its cloud, name, kind and host, its events, files and stored size, what parses, tails or indexes, and the folder of its stored logs with Reveal in Finder and Copy Folder Path. An instance without a license adds Read only without a license
- Open Instance…, the + after the tabs, lists your connections and the instances with stored logs. List puts the active one first. Group by Kind groups them under Production, Staging, Development, Sandboxes and Other instances, then Stored logs only for stored logs without a connection. Each row shows Active, Tab open or No connection, and the size stored, such as 1.2 GB stored
- Right-click a tab for Close Tab, Close Other Tabs, Close All Tabs, Open in Editor Tab and Open in New Window. Drag tabs to reorder them
- An instance without a connection reads No connection, stored logs only. Its stored logs stay readable
Closing a tab asks Close zzrx-001.dx.commercecloud.salesforce.com, for example: Keep Logs keeps the stored logs on this computer for the next time, Delete Logs frees the space. The log files on the instance stay either way, and the instance's tails stop unless another open project shows it. Check Keep logs without asking next time to skip the question
With no tab open
The Log Center shows Choose an instance to open its logs in a tab over the list of instances. The active connection is selected: pick an instance and click Open in Tab, or double-click it. A line under the list counts the stored instances and their size, with Manage Stored Logs…
How it works sits beside the list, or under it when the tool window is narrow:
- Open an instance from the list
- Parse or tail its logs in Files
- Find causes in Issues, Events and Anomalies
- Close the tab to keep or delete its stored logs
With no connections and no stored logs, it reads No connections and no stored logs yet. Add a connection in B2C Connections, see Connections
The views
| View | What it shows |
|---|---|
| Files | The instance's log files and archives, and local files you added, with their state, see Files & Tails |
| Issues | One row per repeated error or warning, with its count, trend, last seen time and source, see Issues & Anomalies |
| Events | Every log entry, newest first, under a timeline of the events by level, see Event timeline |
| Anomalies | What changed against the usual rate: spikes, new errors, regressions, see Anomalies |
| Monitor | What parses or is tailed right now, and what the store holds, see Monitor |
| Storage | Where the instance's stored logs are and their size, see Storage |
Each view's tab shows its icon and count, and resting the pointer on it explains the view. Large counts are shortened, such as 27K or 1.2M, and a + means at least that many while the count runs. Storage shows the stored size instead. The end of the row shows what runs, such as Parsing 2, 1 queued or Tailing 3 files, or Indexing while only the search index catches up, the load, Normal, Elevated or High, and the instance's cloud icon. Rest the pointer on the icon for the instance's card, or click it for Show Stored Logs Location, Delete Stored Logs… and Manage Stored Logs…
In a narrow window the view tabs come first. Their counts go before a name is cut, then what runs and the load give way, and the instance's icon stays
| Title bar button | What it does |
|---|---|
| Export | Saves issues or events as HTML, JSON or Markdown, see Export |
| Create Report | Writes an HTML report and opens it in the browser, see Create Report |
| Open in New Window | Moves the instance to a window of its own |
| Open in Editor Tab | Moves the instance to an editor tab named after it |
| Maximize Log Center | Gives the Log Center the IDE window's whole room. Restore Log Center brings it back |
The gear menu has Manage Stored Logs…, Show Guide, Stop All Log Tails, Copy Agent Fix Workflow, Log Center Settings and Show as Separate Window
Windows and editor tabs
Open in New Window and Open in Editor Tab move the instance's views with their filters, one window or editor tab per instance. A window remembers its place and size, and Back to Tool Window returns it. Closing a window or an editor tab puts the instance back in the tool window. Neither reopens with the project
| Where | Title |
|---|---|
| A window | Log Center: zzrx-001 (Staging): the connection's name, with Production, Staging or Development when the instance has that kind |
| An editor tab | Log Center: zzrx-001.dx.commercecloud.salesforce.com: the host, with the Log Center icon, tinted by kind like the instance tabs |
Show as Separate Window in the gear menu shows the whole tool window, with every instance tab, as a window of its own
Guide
The first time the Log Center opens, a guide of 25 tips walks you through it, view by view. Each tip opens the view it explains and points at the button, field or panel it's about. Its header names the step, such as Tail (3 of 25). Click Next, or Skip Guide to end it, and Got It on the last tip. Show Guide in the gear menu, or in More Actions in a window, runs it again from the first tip
| View | The tips explain |
|---|---|
| Files | Where the logs come from, Parse, Tail and Stop, how to pick several files, More Actions and Add Local File, and the file filters, grouping and sorting |
| Issues | What an issue is, the search and its wildcards, the time range and Filters, the pills and Clear All, an issue's details, Mark Fixed, Move to Backlog and Investigate with MCP, and the row keys |
| Events | Unique and As Recorded, the chart with its legend, zoom and marks, an event's details, Hide Details and the Details strip that brings them back |
| Anomalies | The kinds of anomalies, Detection window and Detect Again |
| Monitor, Storage | The work and its load, and the instance's stored logs: their size, space, limits and folder |
| The Log Center | The instance's icon, the buttons above the views with Open Instance… and the gear menu, which an editor tab doesn't have, then the gutter marks, Highlight lines with log errors and the status bar widget |
The keys and gestures in the tips are the ones of your OS, such as ⌘Click and ⌘⏎ on macOS
On Files, a line under the toolbar says what Parse and Tail do until you click Got It. Show Guide brings it back
How it works
List the files
Files lists the .log and .log.zip files in the instance's Logs and Logs/log_archive folders over WebDAV, with the connection's account
Parse or tail them
Parse reads a file once. Tail parses it, then reads its new lines every second. The first read of a server file comes zipped by the server, later reads fetch only the new bytes
Group the entries
Each entry is stored with its level, file, site, controller and session. Entries whose messages differ only in times, ids, long numbers or counts become one issue
Search the store
Search, filters, counts and charts read the local store, so they stay fast while files parse and work offline
The log text in the details and a live tail in an editor tab read like a log file open in the editor, with the same colours, folds and clickable paths, see Logs in the Editor
The Log Center stays out of the way of your work:
- Parsing runs on its own threads, never on the IDE's UI thread
- It pauses while the IDE indexes, in power save mode and when memory runs low, and the file shows why it waits
- Files of 100 MB and more parse one at a time
- A search through many events shows Searching older events… with a Stop link that keeps what was found so far
Where the data is kept
Each instance has its own folder in <IDE system folder>/intellij-sfcc/log-center/, named after its host. The files on the server never change
| What | Where | How to remove it |
|---|---|---|
| Parsed events and the search index | The instance's folder, shown on Storage | Delete Stored Logs… on Storage, Delete Logs when you close the tab, or Manage Stored Logs… |
| Downloaded logs | The IDE's downloads folder, the same as Download and Open in B2C Explorer | Delete the files |
| Reports | .intellij-sfcc/logs-streaming/reports/ in the project | Delete the files |
Events older than Keep events for, days are removed, and an instance never stores more than Maximum size per instance, GB, see Settings
License
Parsing and tailing need a valid license or trial. Without one, running parses stop with No valid license, the tab row reads Read only without a license, and everything stored stays readable, see Purchase & License
Settings
Open Settings › Tools › Intellij SFCC › Log Center, or Log Center Settings from the gear menu. The settings apply to every project
| Setting | Default | What it does |
|---|---|---|
| Parse threads | 0 | Threads that parse files, 0 to 8. 0 picks them from your CPU cores. Applies after an IDE restart |
| Tail interval, ms | 1000 | How often tailed files are checked for new lines |
| Refresh remote file list, s | 5 | How often Files reloads the server's list while it shows. A failed listing waits longer each time, up to 5 minutes |
| Levels to parse | All four | New parses skip the levels turned off and lines without a level. Files parsed before keep their events |
| Pause parsing while the IDE indexes | On | Parses wait for indexing to finish |
| Keep events for, days | 30 | Older events are removed |
| Maximum size per instance, GB | 6 | The oldest events are removed above this size |
| Ask whether to keep stored logs when closing an instance tab | On | Off, closing a tab keeps its logs without asking |
| Show details as a full-height sidebar | On | Off, the details sit beside the list under the query bar and timeline |
| Show log issues in the editor gutter | On | Marks the lines that logged errors, see Errors in the gutter |
| Highlight lines with log errors | Off | Also marks the lines in the editor and the Problems tool window |
The Storage group shows how many instances are stored and their size. Compact applies the age and size limits now and frees the space, and Manage Stored Logs… opens the list of stored instances
Keyboard
These keys work when a table has the focus, so J, K and / still type everywhere else
| Key | Keymap action | What it does |
|---|---|---|
J | Log Center: Next Row | Selects the next row |
K | Log Center: Previous Row | Selects the previous row |
Enter | Log Center: Open Row | On an issue, shows its events. On an event, shows its entry |
Cmd+Enter (Ctrl+Enter) | Log Center: Open Row Source | Opens the row's source |
/ | Log Center: Focus Search | Focuses the search |
Cmd+F (Ctrl+F) | Focuses the search from anywhere in the view | |
F4 | Opens the row's source | |
Left, Right, Home, End | On the focused row of view tabs: the previous, next, first or last view |
In Files, only Cmd+F (Ctrl+F) of these works, and it focuses the file search. Its own keys are in Pick files and Groups. The details of an issue or an event move to the previous or next row with the IDE's Previous Occurrence and Next Occurrence keys, see The details
Assign your own keys to these actions in Settings › Keymap. They work in the tables too. Mark Fixed and Move to Backlog have no default keys, and their names turn to Mark Not Fixed and Remove from Backlog on an issue that is fixed or in the backlog
Troubleshooting
| Symptom | What to do |
|---|---|
| No Log Center button | The project has no SFCC code yet, see Projects without SFCC code |
| An instance is missing from Open Instance… | Add its connection, see Connections |
| This connection cannot read server logs; local files only | The account has no WebDAV access to the logs. Check its access keys in Credentials |
| A file stays Waiting: the IDE is indexing | It resumes when indexing ends. To parse during indexing, turn off Pause parsing while the IDE indexes |
| A file reads Stopped with No valid license | Activate a license or trial, then click Parse or Tail again |
| Info or debug lines are missing | Turn the level on in Levels to parse and parse the file again |
| The store grows too large | Lower Keep events for, days or Maximum size per instance, GB, then click Compact, or delete instances in Manage Stored Logs… |
| No active instance. Pick a connection to see its logs | Pick a connection in the main toolbar, or open an instance from Open Instance… |
| The views read Opening the Log Center store… | The instance's store is opening. The views fill when it opens |
| Could not open the Log Center store: … | The views show the reason instead of an empty table. Close the tab and open it again, or delete the stored logs in Manage Stored Logs… |