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
Why we removed AI solutions from Flare
AI generated solutions are dead, long live AI generated solutions! We removed the old one-shot fixes from a model that could only see the stack trace. It simply couldn't compete with modern agentic AI. In their place, Flare works with the agentic AI tools you already use: an MCP server that handles real triage, a CLI with an agent skill, quick Copy for AI prompts in the UI and docs served as markdown. Hosted agents are in the works too.
Alex
Flare now uses OAuth for MCP, the CLI, and API
Connect MCP clients like Claude and Cursor to Flare by logging in from your browser, no more copying API tokens. Every connection gets its own permissions, so you can give your AI read-only access to a single project. The CLI signs in the same way, and new personal access tokens with scopes and expiry cover scripts and CI.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates