Skip to main content

See where your Apex spent its time.

Open a Salesforce debug log in VS Code to get a flame chart of the transaction, its call tree, and every SOQL query, DML statement and governor limit it used.

Free and open source under the BSD-3-Clause license.

Live demo of a 20 MB sample log, in your browser
Apex Log Analyzer showing a 24.6 second transaction: the Timeline flame chart with its minimap and governor limits strip, beside the Inspector overviewApex Log Analyzer showing a 24.6 second transaction: the Timeline flame chart with its minimap and governor limits strip, beside the Inspector overview

Built for large logs 100 MB+

Each row compares a release with the one before it. A shorter bar costs less. See the release notes

  • Large log ready12.4× faster965 ms to 78 ms on a 100 MB logv1.24
  • Memory after opening a large log90% less488 MB to 47 MB on a 100 MB logv1.24
  • Zoom and pan the Timeline7× fasterv1.20
  • Search a large logUp to 10× fasterv1.20

Visualize, analyze and optimize

  • Timeline

    See where the time went

    A flame chart of the whole transaction.

    • Large logs ready 12× faster in v1.24
    • Zoom and pan 7× faster in v1.20
    • Search up to 10× faster in v1.20
    • A minimap and a governor limits strip
    Timeline docs
    Timeline tab: a flame chart of a 24.6 second transaction with its minimap, governor limits strip and the Inspector overviewTimeline tab: a flame chart of a 24.6 second transaction with its minimap, governor limits strip and the Inspector overview
  • Call Tree

    Follow the execution

    Every call, with what it cost.

    • Tables respond up to 30× faster on large logs in v1.24
    • Expand, filter and scroll 3× faster in v1.16
    • Go to Code 6× to 10× faster in large projects in v1.22
    • Three views: Time Order, Aggregated and Bottom-Up
    Call Tree docs
    Call Tree tab: nested methods with total time, self time, SOQL, DML and heap columnsCall Tree tab: nested methods with total time, self time, SOQL, DML and heap columns
  • Database

    Find the slow queries

    Every statement that touched the database.

    • Every SOQL, SOSL and DML statement, with time and rows
    • Selectivity and the query plan for each SOQL query
    • Usage against each governor limit, as used / limit
    Database docs
    Database tab: SOQL and DML statements with timings, row counts, selectivity and governor usageDatabase tab: SOQL and DML statements with timings, row counts, selectivity and governor usage
  • Inspector

    Inspect anything

    Select a frame, a row or a statement to see it in depth.

    • The Local and Static variables at any frame, with Apex Code at FINEST
    • Every value a variable held across the calls of a merged row
    • With nothing selected, the limits nearest their ceiling and the log findings
    Inspector docs
    Inspector reading the whole log: the governor metrics nearest a limit, the log findings, and how few signatures hold its self timeInspector reading the whole log: the governor metrics nearest a limit, the log findings, and how few signatures hold its self time
  • Governor limits and heap

    Stay inside the limits

    How close the transaction came to its limits and heap, and where.

    • Heap for every method and call path, as Net, Gross and Peak
    • Tells allocate-then-free churn apart from a real leak
    • Every governor limit plotted over time
    • The call path that used each limit stands out in the Call Tree
    Governor limits and heap docs
    Governor limits strip under the Timeline, with a tooltip listing CPU time at 94.4% of its limit, DML rows, SOQL queries and heap sizeGovernor limits strip under the Timeline, with a tooltip listing CPU time at 94.4% of its limit, DML rows, SOQL queries and heap size
  • Analysis

    Find the hot Apex

    The methods that cost the most, ranked.

    • Every method in the log ranked by self time
    • Group by caller namespace to see whose package costs the time
    Analysis docs
    Analysis tab: methods ranked by self time and grouped by typeAnalysis tab: methods ranked by self time and grouped by type

Works with any Salesforce .log file. Runs in VS Code 1.102 or later, and in vscode.dev, github.dev and the Salesforce Web Console.

Use the same parser outside VS Code

Apex Log MCP Server

Ask GitHub Copilot Chat, Claude Code, Cursor or any MCP client what is slow in a log.

  • Summarizes duration, governor limits and fatal errors
  • Ranks methods, SOQL, DML and flows by self time
  • Runs anonymous Apex in an org, and asks first in production
  • Runs on your machine with Node.js 22 or later, and needs no API keys
npx -y @certinia/apex-log-mcp

Apex Log Parser

The parser behind the extension and the MCP server, for your own tools.

  • 171 event types, each parsed into its own class
  • An event tree with each entry matched to its exit
  • Self and total time for every node, in nanoseconds
  • Governor limits per namespace, and no dependencies
npm install @apexdevtools/apex-log-parser

Open your first log

  1. Install Apex Log Analyzer from the VS Code Marketplace.
  2. Open a .log file, or run Log: Retrieve Apex Log And Show Analysis to get one from your org.
  3. Click Log: Show Apex Log Analysis at the top of the file.