Skip to main content

Explore the Apex Log Analyzer for Salesforce debug logs features including interactive timelines, detailed Time Order, Aggregated, and Bottom-Up call trees, in-depth analysis, database insights, and powerful search capabilities to streamline your debugging and performance tuning.

🪪 Log info​

The header names the log's entry point, the user and the start time. Hover it for the full details. When the log has more than one entry point, the header names the longest and counts the rest, and the tooltip lists the top five.

🚦 Log problems and notifications​

Log problems are problems found in the log itself - governor limit exceptions, fatal errors, skipped lines. A chip shows the worst severity's icon with a count badge, and a tick when the log is clean. Notifications are messages about the tool rather than the log - today, parser diagnostics for log lines it couldn't understand. The two are kept apart so they don't read as one severity count.

  • In a truncated log, each skipped section states how much of the log it dropped.
  • A file that holds several logs shows the first log and flags the rest.

Each opens as a list of cards: a severity icon, a summary, a dimmed line with the kind and the time in the log (e.g. Fatal error · 24.6 s), a message that expands on click if it runs past two lines, and - for problems that point at a spot in the log - an arrow action that jumps to it in the Call Tree.

If the parser meets a log event it doesn't recognize, a notification card carries a Report unsupported log event action, opening a pre-filled GitHub issue.

🎚️ Debug levels​

A row of dropdowns shows the debug levels the log was captured with, one per category (e.g. APEX_CODE FINE). Choose a lower level to see every tab as if the log had been captured at that level. For example, set APEX_CODE to DEBUG to hide method entries and keep queries and the System.debug lines written at DEBUG or above.

  • An event finer than its category's level is hidden. Its own time is added to the nearest event that stays, so totals do not change.
  • In each dropdown, the level the log was captured at is marked logged. A finer level is greyed out: the log does not hold that detail.
  • A category set below the level the log captured is highlighted.
  • Filters, columns, sort and the Timeline zoom stay as they were.
  • A query keeps its query plan while the query shows.
  • In the inspector, Variables shows what the log holds, whatever level you choose.
  • A section that a lowered level empties names that level, and how to show the data again.
  • Choose the logged level again, or select Reset (↺) after the dropdowns to reset every category at once.

••• Menu​

The ••• menu holds Help and Report an issue. When the window is narrow, it also holds the header items that no longer fit.