Files lists the log files of the instance in the tab, and the local files you added. Parse reads a file once, Tail keeps reading the new lines the instance writes
Sandbox 01
version2
Files
Issues
Events
Anomalies
Monitor
Storage
Parse
Tail
Parse New Data (3)
RefArch (3)
~/Projects/storefront
Parse files
Check one or more files and click Parse. The row shows the progress, then the number of events read. Double-click a file, or press Enter, to see its events. It's parsed first if it has none yet, if its last parse failed or stopped, or if it grew since, and Events fills as it parses
The tab counts every listed file, such as Files 42
Until you click Got It, a line under the toolbar says what Parse and Tail do and how to pick several files. Show Guide in the gear menu brings it back
| Button | What it does |
|---|---|
| Refresh | Reads the file list from the server again |
| Parse | Parses the checked files once, archives too |
| Tail | Parses the checked files, then follows the new lines the instance writes, see Tail files |
| Stop | Stops parsing or tailing the checked files |
| Parse New Data (3) | Shows while parsed files grew, with how many did. Parses only what was added since their last parse, and its tooltip says how much |
| Add Local File | Parses a log file or archive from this computer, see Local files |
| More Actions | Show Events, Tail in Editor Tab, Download and Open, Reveal in B2C Explorer, Clear Events, Delete Stored Data, Parse New Data, Tail All and Stop All |
| List, Group by Type, Group by Prefix | One list, or groups under headers that open and close. Expand All and Collapse All show while grouped |
File actions
Right-click a file for every action. Right-clicking a group header checks that group's files, so the menu acts on all of them
| Action | What it does |
|---|---|
| Parse, Tail, Stop | The same as the toolbar buttons |
| Show Events | Shows the file's events, parsing it first if it has none yet |
| Tail in Editor Tab | Opens the live tail of a tailed or local file in an editor tab, see Tail in an editor tab |
| Download and Open | Saves a copy of the server log in the same downloads folder as B2C Explorer and opens it |
| Reveal in B2C Explorer | Selects the server log under Log Files in B2C Explorer |
| Clear Events | Removes the stored events of the files and keeps them listed |
| Delete Stored Data | Asks Remove 3 files and their events from the Log Center? Files on the server stay., then removes them |
| Stop All | In More Actions: stops every parse and tail of this instance |
Pick files
- Check a row's box, or the header box for every shown file. Cmd+Click (Ctrl+Click) and Shift+Click check several rows. A group header's box checks its files, and shows whether all, some or none are checked
- Filter files by name narrows the list as you type
- Click a column header, File, Blade, State, Events, Size or Modified, to sort by it, and click it again to reverse. Events, Size and Modified sort highest or newest first, File and Blade A to Z. Files with no blade or no events go last. The sort and the column widths are remembered
The pills above the list filter the files:
| Pill | Values |
|---|---|
| Type | The file types, such as Error, Jobs or Custom |
| Prefix | The first part of the file name, such as customerror or jobs |
| Custom log | The file name prefix given to Logger.getLogger |
| Blade | The application server SFCC names in the file name, such as blade4-6-0 |
| State | Not parsed, Parsing or tailing, Parsed, New lines on the server, Stopped, Failed |
| Location | On the server, On this computer |
| Modified | One of Last hour, Last 24 hours or Last 7 days. Picking one replaces the other |
Each value shows how many files it holds. A pill shows only when it can narrow the list: Custom log when a custom log is listed, Blade with more than one blade, and Location with both server and local files
| Empty text | When |
|---|---|
| No files match the filters | The search or pills hide every file. Click Clear All |
| Listing server log files… | The list loads. Each Refresh shows Refreshing the file list… in the status line |
| Could not list server log files | The list could not be read from the instance. The reason follows, with Try Again |
| No log files | The instance has none yet |
The status line counts the files, for example 42 files, 30 parsed, 2 tailed · 3 with new data · 12 shown · 2 selected. 12 shown appears while the search or pills hide some
Groups
Group by Type and Group by Prefix put a header before each group: its name, how many files it holds, their size and updated 5 min ago for its newest file. The header of the group at the top stays pinned while its files scroll under it
- Click a header to open or close its group, or press Left and Right on a selected header. Right on an open header moves to its first file, and Left on a file selects its group's header. Space on a header checks its group
- When files of a group grew since their last parse, its header offers Parse new 120.4 kB with how many files grew, such as 3 files. Click it to parse only that group's new lines
File states
| State | Meaning |
|---|---|
| Not parsed | Listed on the server, not read yet |
| Queued | Waits its turn to parse |
| Parsing 58% | Being read |
| Waiting: the IDE is indexing | Paused for indexing, power save mode, low memory or a free parse thread, and resumes by itself |
| Parsed | Read to the end. When the file grew since, the cell shows Parse new 579.12 kB. Click it to read only the new lines. Its tooltip says The server added 579.12 kB to this file since its last parse, or, for a local file, This file grew by 579.12 kB since its last parse |
| Tailing, checked 1s ago | Tailed, with the time of the last check |
| Stopped | Stopped by you, or by a missing license |
| Failed: … | The read failed, with the reason |
Tail files
Tail parses a file to its end, then reads its new lines every second. The status bar shows how many files are tailed
- Tail All in More Actions tails every log file of the instance that isn't tailed yet. It skips archives, and above 20 files it asks first, such as Tail 42 log files of zzrx-001.dx.commercecloud.salesforce.com?. When every file is tailed already, the status line says Every log file of the instance is tailed already
- Archives can be parsed, not tailed
- Tails resume when you open the project again, for the instances with a tab and the active connection
- Stop All Log Tails in the gear menu stops every tail
- How often files are checked is the Tail interval, ms setting, see Settings
Status bar
The Log Center widget in the status bar reads, for example, 12.4K events · Parsing 2 · Tailing 3, with a bar while files parse and a beating dot while they're tailed. Rest the pointer on it for a card of every instance, and click it to open the busy instance on Monitor. For all it shows and how to hide it, see Status bar
Tail in an editor tab
Tail in Editor Tab in More Actions opens a tailed or local file in an editor tab named Tail: error-blade3-4-appserver-20261029.log, for example. New lines show as they arrive
| Button | What it does |
|---|---|
| Pause | Stops adding new lines while paused |
| Clear | Empties the tab |
| Show in Log Center | Shows the file's events in Events |
A file that isn't tailed reads Not tailed: start Tail in Files. The tab isn't reopened with the project. For the log viewer the tab uses, see Logs in the Editor
Monitor
Monitor lists what parses or is tailed right now and follows the store as new lines arrive
| Column | Shows |
|---|---|
| File | The file |
| Blade | The application server in the file name, such as blade4-6-0 |
| Mode | Parse once, Parse and tail or Tail new lines |
| State | Queued, Waiting: the IDE is indexing and other reasons, Parsing, or Tailing, checked 1s ago |
| Read | How much of the file is read, of its size |
A thin bar under Read fills as the file parses
Under the list, figures sum up the instance. In a narrow window they wrap onto more lines
| Figure | Shows |
|---|---|
| Events | The events stored for the instance |
| Files | The files stored. While files parse, the caption reads how many parse and wait, such as 2 parsing, 1 queued |
| Search index | Up to date, or how many events are still to index, captioned Events still to index |
| On this computer | The store's size on disk |
| Server load | The Log Center's share of your CPU: Normal, Elevated, High or Unknown |
The State, Type and Blade pills and a name field filter the rows. State keeps files that are queued, waiting, parsing or tailing. Stop stops the selected row, Tail in Editor Tab opens its tail in an editor tab and Stop All stops every parse and tail of the instance
With nothing running, it reads Nothing is parsing or tailed. When the filters hide every row, it reads No files match the filters with Clear All
Storage
Parsed events stay in a SQLite store on this computer, one per instance. Storage shows the instance's store first, then every instance's stored logs
Delete All…The tab keeps each part to a line. The top one names the instance with its cloud icon and connection name, then its kind, its host and when the store last changed, such as Updated: Moments ago. An instance without a connection reads No connection, stored logs only there. Figures with icons follow:
| Figure | Shows |
|---|---|
| On this computer | The store's size on disk, which the Storage tab also counts |
| Events | The events stored |
| Files | The files stored |
| Time span | How long the events cover, such as 9 days, with the first and last dates under it. Under a day reads Under a day |
| Search index | Up to date, or how many events are still to index, captioned Events still to index |
Under them, a bar splits the space between the store's two files, and the line under it names each with its colour, size and share:
| Part | File | Holds |
|---|---|---|
| Events and issues | log-engine.sqlite | The events and the issues grouped from them |
| Search index | log-search.sqlite | The full text index that Search uses |
The next line shows how close the store is to the limits in Settings, as small meters. The help icon after each says what happens past it:
| Limit | Reads | What happens |
|---|---|---|
| Size: | 1.2 GB of 6 GB | Over the limit, the oldest tenth of the events is deleted |
| Age: | 9 of 30 days, from the oldest event | Older events are deleted |
A meter turns amber from 90% of its limit and red past it. Both limits are checked every 10 minutes. Change Limits… at the end of the line opens the Log Center settings
The last line is the instance's folder with its links. A long path keeps its start and end around an ellipsis, and resting the pointer on it shows the whole path
| Link | What it does |
|---|---|
| Reveal in Finder (Show in Explorer on Windows) | Opens the folder in the system file manager |
| Copy Folder Path | Copies the folder's path |
| Delete Stored Logs… | Deletes this instance's stored logs after asking |
All instances lists every instance with stored logs, this one selected first. Select one to see its Folder:, with links to reveal or copy it, and its Files: on one line. The line under the list counts the instances and their size, such as 3 instances, 4.1 GB, names the folder that holds every store with All stored logs are in …, and ends with Delete All…, which deletes the stored logs of every instance
Before anything is parsed, it reads Nothing stored yet. Parse or tail a log file to store its events here. In a narrow window the figures, the file line and the limits wrap, and long paths lose their middle. Below about 480 pixels the tab scrolls sideways
Manage Stored Logs… in the gear menu, the Tools menu or the home page opens Stored Logs. It lists each instance with its Size, Last Updated and whether its Tab is open, with Open in Tab, Copy Folder Path, Delete and Delete All…. Select one instance to see its Folder and Files. All stored logs are in … names the folder that holds every store, and an empty list reads No stored logs
Deleting asks first, and closes the instance's tabs. The log files on the instance stay
| Delete | Asks |
|---|---|
| One instance | Delete the stored logs of zzrx-001.dx.commercecloud.salesforce.com (1.2 GB)? Its tabs close. The log files on the instance stay. |
| Several instances | Delete the stored logs of 3 instances (4.1 GB)? Their tabs close. The log files on the instances stay. |
| Delete All… | Delete All Stored Logs: the stored logs of every instance, with their count and size |
Local files
Add Local File parses .log or .log.zip files from your computer, for example ones a colleague sent. Pick one or several in Add Log Files. Each is listed with a local tag and searched like the server files
When you open an SFCC log in the editor, a banner offers Search this log and see its issues and charts in the Log Center. Open in Log Center parses the file and shows its events, Hide hides the banner until the IDE restarts
From B2C Explorer
Right-click files under Log Files in B2C Explorer, see Log Files:
| Action | What it does |
|---|---|
| Open in Log Center | Parses the files, then shows their events. With several files, it opens Files |
| Tail in Log Center | Tails the files, then opens Monitor. Archives are left out |
Troubleshooting
| Symptom | What to do |
|---|---|
| Could not list server log files | Check the connection and its access keys, then click Try Again |
| This connection cannot read server logs; local files only | The connection has no WebDAV access to the logs. Check its access keys in Credentials |
| A file shows Parse new … | The server file grew. Click it, or Parse New Data for every grown file, or Tail to keep it current |
| Tail is disabled | The checked files are archives, or tailed already. Archives can only be parsed |
| Tail in Editor Tab is disabled | Select one tailed file, or one local file |
| B2C Explorer does not list … | Refresh Log Files in B2C Explorer and try again |