A diagnosis, not a data dump
A debug log will happily tell you 168,000 things. Almost none of them matter. Saasy Logs ranks what does — here's real output from a 25 MB log that blew its CPU limit.
| Severity | Finding | Where |
|---|---|---|
| CRITICAL | CPU time exceeded: 30,064 of 25,000 (120%) | namespace (default) |
| ERROR | System.LimitException: Apex CPU time limit exceeded | findTriggerRelations, Apex line 22 — 5 occurrences |
| WARN | Log is incomplete — Salesforce discarded 35.8 MB | Timings across the skip are unreliable |
| WARN | 8.88 s unlogged gap (3% of transaction) | line 113,890, between VALIDATION_PASS and managed package |
| INFO | 104.5 s self time in updateTasks |
25 calls · 125 s total · 25 DML — DML inside a loop |
Where the project actually is
One tier works today. The other two are honest roadmap, not shipping product — marked with ○ below.
- Ranked findings: exceptions, blown governor limits and the biggest unlogged time gaps, sorted by what will actually help you
- Self-time hotspots: which method burned the time, excluding its children, across every call
- Log scrubber: strip record IDs, emails and field values before you paste a log into a ticket
- Honest about incomplete logs — flags Salesforce truncation instead of inventing timings
- Paste-only by design: no Drive permission requested, nothing leaves your spreadsheet
- Batch folder parsing straight from Google Drive
- Custom noise filters and saved analysis profiles
- Colour-coded exception traces and clear/append control
- Scrub profiles for regulated orgs
- Cross-log analysis: rank methods by self time across twenty logs, not one — find the pattern a single log can't show
- Governor limit trends over many transactions
- Chunked handling of very large logs
- Team licensing for consultancies
🔒 Privacy Policy
Apex debug logs are among the most sensitive artefacts a Salesforce org produces. They routinely contain record IDs, email addresses, field values and the shape of your internal automation.
Saasy Logs does not collect, store, transmit or receive your log data. Parsing happens entirely inside the Google Apps Script runtime attached to your own spreadsheet. The add-on makes no external network requests, contains no analytics or tracking, and requests no Google Drive permission at all — it can only see the spreadsheet you open it from.
We operate no server and hold no account for you, so there is no database in which your data could exist. Anything you paste stays in your spreadsheet and is yours to delete.
Last updated 11 August 2026 · Questions: support@saasylogs.com
📄 Terms of Service
Saasy Logs is provided free of charge and as is, without warranty of any kind. It is a diagnostic aid: it reports what a debug log contains and flags where a log is incomplete, but it cannot guarantee that every performance problem in your org will be surfaced, and it is not a substitute for your own engineering judgement.
You are responsible for ensuring you have the right to process any log you paste into it. Do not use it on data you are not permitted to handle.
Not affiliated with, endorsed by, or sponsored by Salesforce, Inc. or Google LLC. Salesforce, Apex and related marks are trademarks of Salesforce, Inc.
Last updated 11 August 2026