Flare is an easy-to-use beautiful error tracker for PHP and JS built by open source veterans Spatie.
If you're using Laravel to built apps, using Flare is a no-brainer as it is the only error tracker with many very specific optimizations that give you unprecedented insights in your errors.
In these docs, we'll give you a detailed overview of everything Flare has to offer.
Why do you need an exception tracker in the first place?
If something goes wrong in your production environment, and you don't use an error tracker, it is very easy to miss that an error happened. If you're lucky, one of your users will contact you about it (which is a bit embarrassing), or they won't contact you about it (which is even worse, because you won't have a chance to fix things).
When you use an exception tracker like Flare, your app will send the error to Flare, and Flare will send you a notification via Mail, Slack, or ... The notification will contain a link to a full report on the error giving you as much details as possible about. You can use all of this information to fix your app, even if your user doesn't contact you about it.
What makes Flare the best error tracker?
At Spatie, we build and maintain very large apps ourselves. We noticed that existing error trackers have confusing UIs that bombard you with too much information. We built Flare with ease of use in mind. Our aim is to show you the most relevant information, so you can fix error faster in all your PHP and JS applications.
Why is using Flare a no-brainer for Laravel developers?
If you use Laravel, you probably already are familiar with how Flare looks like. When you have an error is happening in your local Laravel app, you'll see an error page. That error page was made by us - it's called Ignition.
Inside Flare, errors are displayed similarly as they would appear on Ignition, you already know where the important bits of info are. We've gone the extra mile to report errors from a Laravel app: we recognize Livewire errors, for an error in a queue job we display information about that queue, view errors will contain the decompiled Blade view, ...