By default, Ignition and the Flare PHP client (if you're using Flare in a non-Laravel application) will always send all the exceptions and errors to Flare.
In the cases where you don't want all exceptions being sent to Flare, you can from now on filter the exceptions sent using a callback:
// in ignition
Flare::filterExceptionsUsing(
fn(Throwable $throwable) => !$throwable instanceof AuthorizationException
);
// in the flare-php-client
$flare->filterExceptionsUsing(
fn(Throwable $throwable) => !$throwable instanceof AuthorizationException
);
When a PHP error is thrown, you can now configure which levels of errors should be sent to Flare:
// in ignition
Flare::reportErrorLevels(E_ALL & ~E_NOTICE);
// in the flare-php-client
$flare->reportErrorLevels(E_ALL & ~E_NOTICE);
In this case, Flare will send all PHP's internal errors except E_NOTICE errors.
Continue reading
Track frontend errors back to the exact commit
Swap the default random UUID for your git commit hash and trace every JavaScript error straight back to the deploy that caused it.
Dries
A unified error debug timeline
We've reworked the error debug timeline to show all events in chronological order and added support for HTTP requests, Redis commands, filesystem operations, and caching events.
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates