Insights
New teams will now see an example project
Freek
When people first create their Flare account (or create a new team within their account), they are greeted with instructions on how to send a first error to Flare. They would only see what an error in Flare looked like once they'd sent one themselves.
For people new to Flare, we wanted to make it easier to immediately see what errors look like and showcase some of the cool things we do when rendering particular errors. That's why new accounts and teams will now see an example project added to their account.

This project contains some nice example errors, like this one where we have code highlighting for the SQL query.

There's also an example error where we show the list of URLs where it occurred (all fictional URLs for this example).

And, of course, we also show an error that uses one of our defining features: solutions.

We hope this example project makes it easier for people to see that Flare can beautifully display all errors.
Continue reading
Introducing Flare’s next big feature: performance monitoring
Flare's new Performance Monitoring feature is now live, giving you complete visibility into your Laravel app's HTTP routes, queued jobs, Artisan commands, and database queries.
Freek
Lessons from the deep end
20 months ago, we started building Performance Monitoring as Flare’s next big feature, never expecting Laravel’s rapid commercial growth to put us in direct competition with their own tools. This is our honest take on those 20 months went, how we’re adapting to this new reality, and where we’re heading next while staying true to who we are. A dive into the deep end, without knowing how far down it goes.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates