Frequently asked questions

Short answers to common questions about Flare. Most answers link to a page with more detail.

Quotas and usage

What counts as an occurrence, a span, and a log?

An occurrence is one time an error happens in your application. Flare groups occurrences of the same error into one error. If the same error happens 100 times, you have one error with 100 occurrences. Your error quota counts occurrences, not errors.

A span is one measured operation inside a trace, such as a database query, a rendered view, or an external HTTP call. A single request usually produces several spans. Your performance quota counts spans. See how performance monitoring works.

Each log line your application sends counts as one log.

Do occurrences of resolved or snoozed errors count toward my quota?

Yes. Every occurrence that Flare stores counts toward your quota, whatever the status of the error. Resolving or snoozing an error changes how Flare shows it and notifies you about it. It does not stop new occurrences from being stored.

What happens when my team reaches its quota?

Errors, spans, and logs each have their own monthly quota. When a quota is used up, Flare stops accepting new data of that type until the quota resets or you upgrade your plan. The other types keep working while they still have quota left. For example, when the error quota is used up, Flare still accepts spans and logs. And reaching your span or log quota never stops new errors from showing up in Flare or the notifications about them.

Flare emails the team owner and the billing contacts when the team has used 80% of a quota, and again when the quota is reached.

When does my quota reset?

On a paid plan, quotas reset every month on the day your billing period started. Yearly plans also reset every month. The email Flare sends when you reach a quota tells you when your usage resets.

How do I get more quota?

Upgrade to a bigger plan on the billing page of your team. The quotas of the new plan apply right away, and Flare accepts new data again within a few minutes. Already on the highest plan? Get in touch.

How can I use less of my quota?

• Lower the trace sample rate. Flare does not receive spans for traces that are not sampled. See sampling for Laravel, PHP, and JavaScript.
• Set a minimal log level, so only important logs are sent. See log levels for Laravel and PHP.
• Stop sending exceptions you don't need. See ignoring collected data for Laravel and PHP.
• Keep spike protection turned on.

Does spike protection affect my quota?

Spike protection stops a sudden burst of errors from using up your error quota. While it is active, Flare stores only one occurrence per minute and discards the rest. Discarded occurrences do not count toward your quota. You can turn spike protection off in the project settings. See spike protection.

What happens if my team has more projects or members than my plan allows?

Flare stops accepting new errors for the team. To start receiving errors again, upgrade your plan or remove projects or team members. Example projects do not count toward the project limit.

Errors and data

How long does Flare keep my data?

Flare keeps errors, traces, and logs for 30 days. Older data is removed automatically.

An error can show a total occurrence count that includes occurrences older than 30 days. To filter on that total, use the occurrence_count_historic directive. See searching errors.

Do resolved errors come back?

Yes. When a resolved error occurs again, Flare marks it as unresolved, and it shows up in the error list again. You can get a notification when this happens. See notification events.

A snoozed error is unsnoozed when the snooze period has ended and the error occurs again. See snooze.

Why don't I see errors caused by browser extensions?

The JavaScript client ignores errors that it thinks come from a browser extension, because that code is not part of your app. To report them, set the reportBrowserExtensionErrors option to true. See reporting errors.

Can I send data from different environments to one project?

Yes. Flare does not enforce environments, so you can send data from any environment to any project. See getting started.

Can I keep sensitive data out of Flare?

Yes. The Flare clients can censor data before it leaves your application, such as client IPs, request and response body fields, headers, cookies, and session data. See censoring collected data for Laravel and PHP.

Trial and billing

How does the free trial work?

Every new team starts with a 10-day trial. No credit card is required. The trial includes 1,000 error occurrences, 500,000 spans, and 100,000 logs.

When the trial ends, Flare stops accepting new data until you choose a plan. A team admin can extend an expired trial once by 10 days on the billing page of the team.

Can I change my plan?

Yes. You can switch plans on the billing page of your team. Plans are billed monthly or yearly. The quotas of the new plan apply right away.

What happens when my subscription ends?

Flare keeps accepting data until the end of the period you paid for. After that, Flare stops accepting new errors, traces, and logs from your projects.

AI features

Which AI provider does Flare use?

The Flare Assistant, AI-written issues, and docs search use OpenAI. Team admins can turn off AI features on the AI settings page of the team. Flare then sends no error, log, or performance data of that team to OpenAI. Docs search queries still go to OpenAI.

The MCP server and the CLI work with whichever AI tool you choose.

Is AI usage included in my plan?

Yes. Every team gets 5 million AI tokens per month for the Flare Assistant and AI-written issues, also during the trial. The tokens reset together with your quotas. When a team reaches the limit, these features stop until the next reset, so there is never an extra bill. The MCP server and the CLI do not use these tokens.

Supported platforms

Which languages and frameworks does Flare support?

• Laravel and PHP: errors, performance monitoring, and logs. See the Laravel and PHP installation guides.
• JavaScript: errors, tracing, and logs in the browser, with guides for React, Vue, Svelte, Alpine, and Inertia. React Native and Electron support error tracking. See the JavaScript quick start.
• Other languages: the Flare protocol describes the payloads Flare accepts, so you can send data from your own client.