Flare by Spatie
    • Error Tracking
    • Performance Monitoring
    • Logs Coming soon
  • Pricing
  • Docs
  • Insights
  • Changelog
  • Back to Flare ⌘↵ Shortcut: Command or Control Enter
  • Sign in
  • Try Flare for free
  • Error Tracking
  • Performance Monitoring
  • Logs Coming soon
  • Pricing
  • Docs
  • Insights
  • Changelog
    • Back to Flare ⌘↵ Shortcut: Command or Control Enter
    • Try Flare for free
    • Sign in
Flare Flare Laravel Laravel PHP PHP JavaScript JavaScript React React Vue Vue Protocol Protocol
  • General
  • Installation
  • Censoring collected data
  • Ignoring collected data
  • Flare daemon
  • Laravel Octane
  • Laravel Vapor
  • Errors
  • Introduction
  • Customise error report
  • Customising error grouping
  • Linking to errors
  • Logs
  • Introduction
  • Levels
  • With errors
  • Performance
  • Introduction
  • Sampling
  • Limits
  • Modify spans and span events
  • Data Collection
  • Application info
  • Cache events
  • Console commands
  • Custom context
  • Database transactions
  • Dumps
  • Errors when tracing
  • Exception context
  • External http requests
  • Filesystem operations
  • Git information
  • Glows
  • Identifying users
  • Jobs and queues
  • Laravel context
  • Livewire
  • Queries
  • Redis commands
  • Requests
  • Server info
  • Spans
  • Stacktrace arguments
  • Views
  • Older Packages
  • Laravel Flare V2
  • Laravel Flare V1
  • Ignition

Requests

Flare can collect information about the requests being made to your application. This includes:

  • The request method
  • The request URL
  • The body size & contents
  • The user agent
  • The IP address of the user
  • The request headers
  • The request cookies
  • The request query parameters
  • The request files
  • The request session data
  • The request route
  • The request route parameters
  • Livewire components
  • The authenticated user

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

use Spatie\FlareClient\Enums\CollectType;

'collects' => FlareConfig::defaultCollects(
    ignore: [CollectType::Requests],
),

It is possible to filter out fields from the request body, headers, and the user's IP address. You can read more about this here.

Ignoring specific requests

You can drop traces for individual URLs, paths, or routes by adding patterns to the Requests collect in config.php. When a request matches, the trace is unsampled and no spans are sent for it.

use Spatie\FlareClient\Enums\CollectType;

'collects' => FlareConfig::defaultCollects(
    extra: [
        CollectType::Requests->value => [
            'ignored_routes' => ['horizon.*', 'telescope.*'],
            'ignored_urls' => ['https://example.com/internal/*'],
            'ignored_paths' => ['/health-check', '/metrics/*'],
        ],
    ],
),

Patterns are literal strings with * as a wildcard. Routes are matched once Laravel has resolved the route name, so route patterns are evaluated through deferred sampling.

By default, livewire components passed to the request are also collected. This can be disabled by ignoring the Livewire collect in config.php:

use Spatie\LaravelFlare\Enums\LaravelCollectType;

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

Grouping unmatched route errors

When a request hits a URL that doesn't match any registered route (for example, bots scanning for wp-admin.php), Flare will automatically set the http.route attribute to errors::{status_code} (e.g. errors::404). This groups all unmatched 4xx requests under a single route label instead of cluttering your dashboard with individual URLs.

This behavior is enabled by default. You can disable it in config.php:

use Spatie\FlareClient\Enums\CollectType;

'collects' => FlareConfig::defaultCollects(
    extra: [
        CollectType::Requests->value => [
            'group_unmatched_route_errors' => false,
        ],
    ],
),
Redis commands Server info
  • On this page
  • Ignoring specific requests
  • Grouping unmatched route errors

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
  • Insights
  • Newsletter
  • Changelog
  • Documentation
  • Affiliate program
  • uptime status badge Service status
  • Terms of use
  • DPA
  • Privacy & cookie Policy
Made in by
Flare