A flow just failed in prod. No alert went out. Nobody knows.

See your whole org’s health before it pages you.

Connect an org and the Monitoring hub runs live reliability, sign-in, and governor-limit checks out of the box — failed flows, stuck async jobs, scheduled-job errors, Apex-test failures, login anomalies, and storage/API pressure. No Salesforce Shield required. And it’s honest by design: every number opens to the exact events behind it with a one-click query to reconcile the count against your own org, it tells you how fresh the data is, it marks a guess as a “likely cause” instead of a fact, and it never cries “new problem” when it simply has no history to compare against.

The same org, with and without the Event Monitoring (Shield) add-on:

Without Event Monitoring

Without Shield — live reliability, login and limit checks still run out of the box. The cards that genuinely need Event Monitoring are greyed “needs Shield,” never faked.

With Event Monitoring

With Shield — the same org now surfaces the Apex exception (94 hits · 12 users, flagged act-now) and Lightning errors too, each with a verdict you can drill into.

Why this instead of reading raw logs in a text editor?

One Save in Salesforce can fan out into 13 logs across triggers, flows, async jobs, and UI reloads. Black Widow stitches that chain into a single timeline, separates what users felt from what ran async, and tells you what to fix first — prod logs never leave your machine.

See the project in GitHub

apex-07L4x000.log — 18,442 lines

161.0 APEX_CODE,FINE;APEX_PROFILING,INFO;CALLOUT,INFO;DB,FINEST;SYSTEM,DEBUG;VALIDATION,INFO;WORKFLOW,INFO

212:04:51.0 (12034879)|EXECUTION_STARTED

312:04:51.0 (12041245)|CODE_UNIT_STARTED|[EXTERNAL]|01q4x00000KZ1|CaseTrigger on Case trigger event BeforeUpdate|__sfdc_trigger/CaseTrigger

412:04:51.0 (13002145)|SOQL_EXECUTE_BEGIN|[14]|Aggregations:0|SELECT Id,Status,OwnerId FROM Case WHERE Id IN :caseIds

512:04:51.0 (14882013)|SOQL_EXECUTE_END|[14]|Rows:1

612:04:51.0 (15110023)|HEAP_ALLOCATE|[71]|Bytes:3

712:04:51.0 (16204412)|METHOD_ENTRY|[12]|01p4x00000Aa2|CaseHandler.beforeUpdate()

812:04:51.0 (17334129)|USER_DEBUG|[88]|DEBUG|Processing 1 case record

912:04:51.0 (18772301)|SOQL_EXECUTE_BEGIN|[34]|Aggregations:0|SELECT Id FROM Contact WHERE AccountId=:accId

1012:04:51.0 (19551044)|SOQL_EXECUTE_END|[34]|Rows:6

1112:04:51.0 (20114882)|ENTERING_MANAGED_PKG|[EXTERNAL]|vlocity_cmt

1212:04:51.0 (21887310)|CODE_UNIT_STARTED|[EXTERNAL]|vlocity_cmt.TriggerHandler

1312:04:51.0 (22440190)|DML_BEGIN|[52]|Op:Update|Type:Case|Rows:1

1412:04:51.0 (23998120)|DML_END|[52]

1512:04:51.0 (24550021)|CODE_UNIT_STARTED|[EXTERNAL]|Workflow:Case

1612:04:51.0 (25110933)|FLOW_START_INTERVIEWS_BEGIN|1

1712:04:51.0 (26773410)|SOQL_EXECUTE_BEGIN|[8]|Aggregations:0|SELECT Id,Email FROM User WHERE Id=:ownerId

1812:04:51.0 (27554120)|SOQL_EXECUTE_END|[8]|Rows:1

1912:04:51.0 (28991200)|LIMIT_USAGE_FOR_NS|(default)|SOQL: 41/100 | DML: 1/150 | CPU: 3204ms

2012:04:51.0 (29110044)|USER_DEBUG|[120]|DEBUG|Recursion guard: CaseTrigger re-entry #3

2112:04:51.0 (30557120)|CODE_UNIT_FINISHED|CaseTrigger on Case

2212:04:51.0 (31200410)|CUMULATIVE_LIMIT_USAGE

Reading raw logs in any text editor: open log 1, read thousands of lines, repeat 13 times.

Black Widow — Explain

Drag one folder. See the full transaction. Get recommendations in minutes.

7.4s user waitRecursion in CaseTriggerPlain-English explanationUnder 10 minutes

“Why not just paste it into ChatGPT or Claude?”

Because on a real org you can’t. Prod debug logs are full of PII, org config, and customer data, and most security teams have hard rules against pasting that into an outside model — especially after Drift, Klue, and every other data-exfil headline. Black Widow does the analysis on your machine. No upload, no MCP server, no Salesforce OAuth connection, no IT ticket. Pull your ethernet cable and it still works — you get AI-grade log analysis in the one place cloud AI isn’t allowed to go.

Three steps from noisy logs to a fix list.

Seven core capabilities, no filler.

And more: live org connection, exports, and broader workflow support.

Drowning in Vlocity CPQ logs?

One cart transaction can throw dozens of logs and blow past a context window entirely. Black Widow groups the whole mess into one timeline, shows where the time actually goes (sync vs async), and gives you the per-namespace SOQL / DML / CPU the Vlocity namespace burned — accurate even when the managed code hides its per-line detail.

It won’t decode Vlocity’s obfuscated internals — Salesforce suppresses those for everyone, so no tool can. But if what you need is “where is CPQAppHandler eating my time and governor limits,” that’s exactly what it tells you, locally.

Built by the person it was built for.

I’m Victor — a Salesforce developer who spent years debugging enterprise orgs the way everyone does: a production incident, a folder of debug logs from a single user action, and a text editor at 2 am. The log that mattered was usually truncated at 20 MB — Salesforce silently drops the oldest lines, often including the limit summary you actually need — and security policy meant none of it could go into ChatGPT. Black Widow is the tool I wanted on those nights: it reads every log from the action, stitches them into one timeline, flags truncation instead of pretending the data is complete, and never sends a byte off your machine.

Built in public. Tell us what to fix next.

Black Widow is shaped by the people who use it. Every bug report and idea lands in our public GitHub backlog — no account gymnastics, no black hole.

Prefer the source? Browse all open issues on GitHub.

Free forever for core analysis.

Parsing, transaction grouping, recommendations, and AI analysis (your own key) are free forever. Pro adds the deep dive: drill-down tabs (Tree, Timeline, Queries, Field History, Architect), auto log extraction & live streaming from your org, org metadata enrichment, Shield dashboard, report exports, and files over 10 MB — $19/mo or $190/yr, with a 14-day free trial (no card required).