Flare Error tracking made for Laravel
Features Pricing Docs Blog Log in Start free trial Free trial
  • Docs
  • Videos

Documentation

  • General

    • Welcome
    • Projects
    • Errors
    • Error occurrences
    • Using the API
    • Sharing error occurrences
    • Spike protection
    • GitHub integration
  • Ignition for Laravel

    • Installation
    • Configuration
    • Security
    • Controlling collected data
    • Sending logs to Flare
    • Linking to errors
    • Identifying users
    • Adding custom context
    • Adding glows
    • Writing custom middleware
  • Flare for generic PHP projects

    • Installation
    • Controlling collected data
    • Identifying users
    • Linking to errors
    • Adding custom context
    • Adding glows
    • Writing custom middleware
  • Javascript error tracking

    • Installation
    • Framework integrations
    • Resolving Bundled Code
    • Reporting errors
    • Client hooks
    • Adding custom context
    • Adding glows
    • Solution Providers
  • Solutions

    • Introduction
    • Adding custom solutions
    • Making solutions runnable
    • Using solution providers
    • Writing good solutions
  • Notifications

    • Configuring notifications
    • Mail
    • Slack
    • Telegram
    • SMS
    • Webhooks
    • Discord
    • Microsoft Teams
  • Team management

    • Using multiple teams
    • Subscribing to a plan
    • Receiving invoices
    • Managing team members
    • Inviting guests to projects

Working with errors

Whenever an error gets reported by your application, we show it on the projects page. If you want to know more about the error, click on it to see more details about the last occurrence.

Screenshot of project screen showing list of errors

Filtering errors

On the list of error of a project, you can search for errors. By default, we only show unresolved and unsnoozed errors. To search on error message, exception name, or url just start typing.

Screenshot of searching errors on project screen

To search on a class only prefix your query with class:

Screenshot of searching errors on class on project screen

You can use these prefixes to search on a specific attribute of an error. Additionally you can use is:* filters to query by error status.

  • class

  • message

  • file

  • first_seen_at

  • last_seen_at

  • resolved_at

  • is:resolved

  • is:unresolved

  • is:snoozed

  • is:unsnoozed

  • is:recent

Resolving errors

You can resolve an error to inform anybody working on a project that the problem has been fixed.

Screenshot of resolved error

Snoozing errors

If you don't want to get notified about new occurrences coming in you can snooze the error.

Screenshot of snoozing options

Deleting errors

Should any of the occurrences of your error contain sensitive data, you can delete the error by clicking "Delete" on the top left corner.

Screenshot of error deletion confirmation

After confirming the deletion, we will delete the error and all of its occurrences from our systems. This action cannot be reversed.

Previous topic Next topic

On this page

  • Filtering errors
  • Resolving errors
  • Snoozing errors
  • Deleting errors

About Flare

  • Home
  • Features
  • Pricing
  • Support

Resources

  • Blog
  • Changelog
  • Docs
  • Ignition

App

  • Log in
  • Start free trial
SPATIE
  • Service status
  • Terms of use
  • Privacy & cookie policy