Spike protection

Sometimes your app might generate a large number of errors in a short time. Spike protection prevents your plan’s event quota from being consumed too quickly. When a project starts receiving more errors than usual, spike protection activates.

By default, spike protection activates when a project receives more than 60 errors per minute. While active, Flare saves only one error per minute and discards the rest. Every three minutes, Flare checks recent activity to decide whether to extend or disable spike protection.

You can change all three values in the project's spike protection settings: the trigger threshold, the occurrences allowed while active, and the check interval.

You can turn this feature off in your project settings. Flare will notify you whenever spike protection is activated or deactivated.

Trigger history

Your project's spike protection settings show a "Trigger history" table. It lists when spike protection started and ended, for the 5 most recent times it was active. The table only appears after spike protection has been active at least once.