Every error, with the context to fix it
A stack trace tells you where it broke. LaraBug sends the request, the query that ran, the job that dispatched it and the user it happened to, so the first thing you read is the whole story rather than the last line of it.
Grouped, not repeated
The same exception from a thousand requests is one issue with a thousand occurrences. Fingerprinting is on the exception class, the file and the line, so a stack trace that shifts by a deploy does not split into a second issue.
- Occurrence counts and a first- and last-seen timestamp on every issue
- Re-opens itself if it comes back after you marked it fixed
- Snooze the ones you already know about instead of muting the project
The whole request, not just the trace
Every occurrence carries the route, the method, the payload, the headers, the session and the authenticated user, next to the source of the file it broke in with the reported line marked.
- Source context around the failing line, straight from your release
- Request payload and headers, with the keys you name filtered out
- The user it happened to, when you pass one
Share one without sharing your account
Every issue has a public link you can hand to someone who does not have a LaraBug login. It shows the trace and the context, and you can revoke it.
Keep reading
Start catching what your users do not report
Free to start and no card needed. Require the package, paste your project key, and the next exception is in your inbox before you have finished reading this.