SF Log Journey for VS Code
Read Apex debug logs as a story. SF Log Journey opens a Salesforce debug log inside VS Code and shows what happened in it: which classes, triggers and flows ran, how long each one took, every SOQL query and DML save, the governor limits and the exceptions. You can follow it as an illustrated journey or in a sober professional dashboard.

SF Log Journey is an independent, open source project. It is not made, endorsed or supported by Salesforce, Inc. "Salesforce" and "Apex" are trademarks of Salesforce, Inc. and are used here only to describe which logs the extension reads.

Two ways to look at a log
Epic journey. Elandor, a small hooded traveler, walks through the log stop by stop on a hand-drawn fantasy map. Every class is a castle, every trigger a bridge, every flow a mill, and the methods are towers. Each stop (a trigger, a query, a save, a flow, a System.debug, an exception…) is told in plain words, with its time and the limits used so far. Monsters mark the problems on the road: a spider on each exception, a troll on queries inside a loop, wolves on repeated queries, dark riders when a limit is almost used up. The rings at the bottom show how close the transaction got to each governor limit.
Professional. A clean dashboard for when you just want answers: did it finish well, what took longest, is there a risk with the limits, and what to fix first. It includes a step-by-step run, a call tree, a timeline, SOQL and DML tables, flows and exceptions.


Switch between them with the button in the panel header, or with the sfLogJourney.interface setting.
Features
- Call tree and timing: total and self time for every method, a flame chart with zoom and a timeline split into chapters.
- SOQL and DML: sortable tables, repeated queries grouped together, filters by object.
- Bad-practice warnings: SOQL or DML inside a loop, the same query run again with the same values, governor limits at 50 % or more. Each warning explains what is wrong and shows an Apex example of how to fix it.
- Governor limits: CPU, heap, SOQL, DML, rows and callouts against their maximum.
- Exceptions and debugs: with their stack trace, log time and a link to the log line.
- Flows: one lane per flow, which decision path was taken and where the time went.
- Async jobs:
System.enqueueJob, @future, batch and scheduled jobs are detected, and the extension links a log to the logs of the jobs it launched when they are in your workspace.
- Jump to code: open the Apex method, query or
System.debug line of any stop, if your Salesforce project (force-app) is open.
- Logs from your org: list and download debug logs with the Salesforce CLI, or listen live while you test and open each new log as it arrives.
- Export report: one offline
.html file (printable to PDF) to attach to a ticket.
- Search and filters, a time heatmap, badges for good practices, keyboard shortcuts, light, dark and high-contrast themes, and English and Spanish.
Getting started
- Install the extension.
- Open the Command Palette and run SF Log Journey: Open a sample log to try it without a log of your own.
- To see one of yours, open a
.log file and click the 🚀 button at the top right of the editor, or run SF Log Journey: Open Salesforce log (also in the right-click menu of the file).
Logs from your org
Install the Salesforce CLI and log in (sf org login web).
- SF Log Journey: Open log from the org lists the debug logs of the project's default org (what launched them, when, how long, size, user and whether they failed). Pick one and the journey opens. Logs are saved to
.sfdx/tools/debug/logs.
- SF Log Journey: Watch live logs from the org turns on a trace flag for your user and opens every new log while you test in Salesforce. Click "Elandor listens" in the status bar to see the logs received or stop.
Commands
| Command |
What it does |
| SF Log Journey: Open Salesforce log |
Opens the current .log file |
| SF Log Journey: Open a sample log |
Opens a sample log to try the extension |
| SF Log Journey: Open log from the org |
Lists and downloads logs with the Salesforce CLI |
| SF Log Journey: Watch live logs from the org |
Opens new logs as they arrive |
| SF Log Journey: Export log report (HTML/PDF) |
Saves a standalone report |
| SF Log Journey: Report a bug |
Opens a prefilled GitHub issue |
Settings
| Setting |
Default |
What for |
sfLogJourney.interface |
journey |
journey (epic journey) or professional (dashboard). |
sfLogJourney.language |
auto |
en, es or auto (follows VS Code). |
sfLogJourney.animations |
auto |
Animations on the map. |
sfLogJourney.sound |
true |
Short sounds and the journey music. |
sfLogJourney.warnings.* |
|
Thresholds for loop, repeated query and limit warnings. |
sfLogJourney.sections |
all on |
Which tabs and parts of the panel to show. |
sfLogJourney.live.* |
|
Minutes, polling interval and auto-open for live logs. |
Privacy
The extension reads logs locally and sends nothing anywhere. The org commands only call the Salesforce CLI on your machine. "Report a bug" opens a GitHub issue in your browser with the extension, VS Code and OS versions and a few numbers about the log (lines, size, API version), never its content.
Feedback
Found a bug or have an idea? Open an issue. Release notes are in the changelog, and the Spanish documentation in README.es.md.
Using a JetBrains IDE? The same extension is available as a plugin for IntelliJ IDEA and the other JetBrains IDEs: see SF Log Journey for IntelliJ.
License
MIT