Flare is an error tracker for Laravel, but what do you do if you want notifications for other events which do not throw exceptions? You might wish to receive notifications for failing payments or other actions that users do in your application and that don't throw errors but where you want to know that they happen.
Since Ignition 1.9.0, Flare supports the collection of logs. You can check out the documentation for this feature here.
The default configuration for the log recording feature of Flare is the log level error, and all logs that happen as Error, Emergency, and Critical trigger a notification instantly. The level for this is configurable at the config file within your application:
// in your config/logging.php
'flare' => [
'driver' => 'flare',
'level' => 'critical',
],
The feature itself can be enabled and disabled in the same file with the key:
send_logs_as_events
Make sure to check our documentation and learn how you get the most out of your Flare subscription.
Continue reading
Version 2 of our JavaScript client libraries
We shipped v2 of @flareapp/js, @flareapp/react, @flareapp/vue, and @flareapp/vite. The framework packages now handle error boundaries, automatic context collection, and component prop capture out of the box. The core client talks to a new, faster ingestion endpoint, and the Vite plugin got retry logic and smarter sourcemap handling.
Sébastien
Flare ❤️ Livewire
Flare has deep Livewire visibility: components nested in traces with full hierarchy, per-phase timing (mount, hydrate, render, dehydrate), aggregated component views with bidirectional links, rich error context, and a lot more. Let us show you how Flare can assist in debugging your Livewire project.
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
