Logging is now available for all Flare users! Send any log from your Laravel or PHP app to Flare and use our polished interface to filter and search your logs in real-time.
Additionally, we added support for logging via JS apps as well.
Why we added logging
Error tracking is useful in many cases, but logs often give you that extra bit of context, especially for new or infrequent errors.
Use logs to understand what an app was doing around the time of an error, trace the lifecycle of a request or job, and spot patterns in production that don't surface as exceptions.
Find what you're looking for by filtering by level, entry type, and time range. Running multiple web workers? Filter by hostname to isolate exactly which server logged what. And we have all your entry points covered: HTTP requests, Artisan commands, queue jobs, and more.
Learn more about how it works in our introduction to logging.
How can I start?
Log collection is part of a new release of our Flare SDKs for Laravel & PHP, so you'll need to update to the latest 3.0 release first. After updating or installing, follow the instructions for Laravel or PHP to configure logging on your app.
If you expect to be sending a lot of logs, we recommend our separate Flare daemon that runs alongside your application. Easy to install on Forge, Laravel Cloud, Kubernetes, or Docker.
It's a free add-on for all plans, with generous limits to get you started.
What's next?
We're working hard to make Flare better, and we can't wait to show you what's next.
If you haven't used Flare yet, or have used it in the past, now is the best time to try out our context-rich Laravel error tracking, logging and performance monitoring. Sign up for a 10-day free trial and get access to all the features.
Continue reading
Create richer issues from your errors
When Flare creates an issue on GitHub, GitLab or Linear, you can now pick the assignee and labels right away.
Ruben
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
