Errors · Getting started
Errors
Every exception your Laravel app reports, and every uncaught error in its pages, grouped into an issue per environment and tied to its release. You hear about new issues, regressions and spikes by Telegram, e-mail or Slack.
Errors is for teams that run a Laravel app and want to know what broke, for whom and in which release, before a customer writes in. The same error a thousand times is one issue with a count, and personal data is scrubbed in your app before anything leaves it.
How it works
| Part | Where it runs | What it does |
|---|---|---|
mybeast/errors-laravel | Your Laravel app | Captures every exception Laravel reports, with no code to write. Writes it to a file, then sends it after the response has gone out. Also makes the browser's config, marks releases and answers Errors' webhook. |
@mybeast/errors | Your pages | Optional. Uncaught errors, rejected promises and React's own, with the clicks and page changes before them. It takes its config from the Laravel SDK. |
| Errors | services.my-beast.com | Groups each error into the issue of its cause, ranks the inbox by the harm each issue does, sends alerts, and keeps a performance view of your routes and jobs once you turn it on. |
An issue belongs to one environment: the same error on staging and in production is two issues. A resolved issue that comes back after its fix reopens as a regression, and each issue shows the release it first came in.
What you need
- A project with Errors on it. Errors' page has the packages.
- A Laravel 12 or 13 app on PHP 8.2 or later, with Laravel's scheduler running.
- For browser errors: a bundler and Node 20 or later. The SDK runs in evergreen browsers.
There is no SDK for other languages yet. Another app can send its errors to the API with a server secret.