Exception tracking
for Laravel.

A Laravel exception tracker collects exceptions from your application so you can see what failed, when it failed, and where it failed in your code. Laritor adds occurrence history, alerts, full stack traces, and related events from the recorded request, job, command, or scheduled task. You can use it for exception tracking alone or extend it to issue tracking and performance monitoring.

Yes. Choose exceptions-only recording to send occurrences that contain an exception, along with their related events. Successful activity without exceptions is discarded. You still get stack traces, occurrence history, alerts, and AI debugging features without recording all application activity.

An exception identifies an error, such as its class, message, and failing code location. An occurrence is an individual time that error happened. Laritor lets you inspect occurrence history and open the recorded request or job associated with a particular failure.

Yes. When a recorded request, job, command, or task contains an exception, Laritor keeps the related events permitted by your recording settings. These can include database queries, logs, outbound requests, cache operations, and custom events. That context helps explain the failure. The occurrence and its related events count toward your usage.

Laravel can report exceptions through its configured logging channels. Laritor gives you a dedicated interface to investigate those exceptions, inspect full stack traces and surrounding code, review occurrence history, and follow recorded events from the affected request or job. It also connects exception alerts to your team’s tools and provides AI-assisted debugging.

Yes. Laritor tracks exceptions from recorded HTTP requests, queued jobs, Artisan commands, and scheduled tasks. From an exception occurrence, open the related execution to inspect its events. This helps investigate background failures as well as errors visible to users.

Yes. The exception details include the error message, class, failing file and line, full stack trace, and a code preview around the failing line. Search the stack frames and inspect application or vendor frames to follow the calls that led to the error.

Configure an integration in Laritor, then enable exception alerts for your application and choose the environments and channels you need. Laritor supports Slack, email lists, Microsoft Teams, Discord, Telegram, GitHub, Linear, and webhooks. GitHub and Linear integrations can create issues containing the exception details and a link to Laritor.

Review its total occurrence count and first and last seen dates, then inspect individual occurrences. Use date and exception class or message filters to find relevant errors. After deploying a fix, check for new occurrences during the period when the affected code runs again.

Laritor’s in-app AI provides explanations, recommendations, and example code based on the exception and recorded context. Alternatively, connect your coding agent through Laritor MCP so it can retrieve exception details and related events, then investigate them with your repository. Review and test the proposed change before deploying it. Each account includes 50 in-app AI prompts per month; you can also connect your own AI provider.

Laritor MCP gives a connected agent access to recorded application data, including exception details, stack traces, and request or job event timelines. The agent can use this context with the code in your repository to understand a failure and work on a fix. Laritor’s data tools provide context; changes to your code happen through your coding agent’s own workflow.

Yes. Customize the Laravel client to redact sensitive strings and fields, anonymize authenticated user information, and control the context you record before it is sent to Laritor. Request and response bodies are disabled by default. Use the customization hooks to remove tokens, passwords, email addresses, or other data your application should not send.

The free trial includes 300K events and 14-day retention. The paid plan starts at $20 per month with 20 million events and 30-day retention. Additional events cost $0.20 per 100K. All three recording modes have the same base price. In exceptions-only mode, you pay for the exception occurrences and related events you send, rather than all successful activity.

An occurrence can include several events. For example, a recorded request with three queries, one log entry, and one exception uses six events when each is 2KB or less: the request, three queries, the log, and the exception. Larger events count in 2KB blocks. Your bill depends on the events and data sizes you send.

Create a Laritor application, install binarybuilds/laritor-client with Composer, and add the application’s connection settings to your environment. Generate an exceptions-only filter and register the generated override in your AppServiceProvider. Run php artisan laritor:sync after deployment, then configure exception alerts in Laritor. The installation and customization guides explain each step.

Yes. Switch to issues-only recording to include detected problems such as failed jobs, failed requests, and slow operations. Choose full observability to also record successful activity for broader performance monitoring. All modes include Laritor features; the choice determines which activity your application sends.