Evidence intake
Drop in the incident
One event per line. ISO timestamps, syslog-style timestamps, bracketed times, and untimestamped lines are all accepted.
Sample evidence loaded. Distill it whenever you are ready.
Operator handoff
The distilled read
The log is still in the intake tray. Distill it to see the highest-signal path and a short list of next checks.
Repeated signatures
No repeated errors yet.
Next three checks
- Distill the log first.
Signal timeline
Copy-ready incident card
Run the distiller to create a Markdown handoff.
The report stays in this tab until you copy or download it.
What this little desk does
It does not diagnose your stack. It counts severity, finds repeated signatures, recognizes likely playback, delivery, DRM, identity, or input/focus families, and turns the result into a short handoff you can paste into an incident doc. The recommendations are prompts for your judgment, not automated truth.
Nothing is uploaded. The log is parsed in this browser tab. No account, server, or log-storage service is involved.
What counts as a repeated signature?
Numbers, IDs, and URLs are replaced with placeholders before messages are compared. That lets “segment 891” and “segment 903” become the same repeated failure instead of two unrelated lines.
FAQ
What log formats does it understand?
There's no strict schema. The page looks for common keywords and patterns — manifest/segment/CDN terms, DRM and key-system names, playback and buffering language, focus/remote-control input, and auth/entitlement terms — across whatever plain-text lines you paste, plus standard severity words like ERROR, WARN, and INFO. Most human-readable smart-TV, player, and DRM logs work even without matching one vendor's exact format.
It picked the wrong "likely focus area"
The focus areas are keyword heuristics, not a certified diagnosis. When a log's language overlaps between families — for example, a manifest fetch that also mentions a token — the distiller can lean toward the wrong one. Use it to narrow down where to look first, not as a final answer.
Does it fetch any of the URLs it finds in my log?
No. The text is only read and pattern-matched in this browser tab. No manifest, segment, or license URL found in a pasted log is ever requested.