Flare by Spatie
    • Error Tracking
    • Performance Monitoring
  • Pricing
  • Docs
  • Insights
  • Changelog
  • Back to Flare
  • Sign in
  • Try Flare for free
  • Error Tracking
  • Performance Monitoring
  • Pricing
  • Docs
  • Insights
  • Changelog
    • Back to Flare
    • Try Flare for free
    • Sign in
Flare Flare Laravel Laravel PHP PHP JavaScript JavaScript
  • General
  • Introduction
  • Installation
  • Censoring collected data
  • Ignoring collected data
  • Laravel Octane
  • Laravel Vapor
  • Errors
  • Adding custom context
  • Customising error grouping
  • Handling errors
  • Linking to errors
  • Reporting errors
  • Sending logs to Flare
  • Performance
  • Introduction
  • Sampling
  • Limits
  • Modify spans and span events
  • Data Collection
  • Application info
  • Cache events
  • Console commands
  • Customise error report
  • Database transactions
  • Dumps
  • Errors when tracing
  • Exception context
  • External http requests
  • Filesystem operations
  • Git information
  • Glows
  • Identifying users
  • Jobs and queues
  • Laravel context
  • Livewire
  • Logs
  • Queries
  • Redis commands
  • Requests
  • Server info
  • Solutions
  • Spans
  • Stacktrace arguments
  • Views
  • Older Packages
  • Laravel Flare V1
  • Ignition

Livewire

When an error occurs in a Livewire component, Flare will automatically collect:

  • The component class
  • The updates made in the request
  • The data present in the component

This data will be collected for all the components in the current Livewire request.

When using performance monitoring, Flare kan keep track of the components being rendered by your application, by default we'll collect the phases a component goes through:

  • mounting / hydrating
  • calls to the component
  • rendering
  • dehydrating

It is possible to combine all these phases into one single span like this:

use Spatie\LaravelFlare\Enums\LaravelCollectType;

FlareConfig::defaultCollects(
    extra: [
        LaravelCollectType::LivewireComponents->value => [
            'split_by_phase' => false,
        ],
    ],
]);

When you want to ignore a specific livewire component from being collected, you can do so by adding the component class to the ignore array:

FlareConfig::defaultCollects(
    ignore: [
        LaravelCollectType::LivewireComponents->value => [
            'ignore' => \App\Http\Livewire\SomeComponent::class,
        ],
    ],
]);

The Livewire functionality is enabled by default, but you can disable it by ignoring the Livewire collect in config.php:

'collects' => FlareConfig::defaultCollects(
    ignore: [LaravelCollectType::LivewireComponents],
),
Laravel context Logs

Catch errors and fix slowdowns with Flare, the full-stack application monitoring platform for Laravel, PHP & JavaScript.

  • Platform
  • Error Tracking
  • Performance Monitoring
  • Pricing
  • Support
  • Resources
  • Blog
  • Changelog
  • Documentation
  • Affiliate program
  • uptime status badge Service status
  • Terms of use
  • DPA
  • Privacy & cookie Policy
Flare