News & updates from the Flare team

Hello there, new API!

You can now retrieve all projects and errors using our new API.

Actions can now be performed on all project errors in one go

When you now check "Select all", all errors of a project can be selected.

Why and how we remove inactive users and teams

Like many others SaaS applications, you can try out Flare using a trial period. Of course, not everybody that tries out Flare will convert. After the trial period is over, some people will not use the service anymore. In this post you'll learn how we clean up the data of inactive teams and users

Meet the new projects overview with error trends and favourites

Our projects overview has been vastly improved.

Create a GitHub issue directly from an email notification

Our email notifications got more powerfull.

How to censor sensitive information in requests to Flare

In some cases, such as a login page, these request fields may contain a password that you don't want to send to Flare. Here's how you can censor certain values.

You can now easily see if an error came from the web, CLI or queue

There's a new "type" property that gets displayed on each error in our UI.

How our GitHub integration works under the hood

Here's a peak at the actual source code of Flare.

Introducing the monthly error report mail

We decided to email the project overview to each user every month.

Introducing our GitHub integration

We're proud to share that errors on Flare can now be associated with issues on GitHub and vice versa. In this post, we'll tell you all about it!

Mail notifications now allow to snooze and resolve errors

When we look at which notification channels our users use, we see that mail is the most popular channel. This motivated us to provide snoozing and resolving abilities to mail notifications.

You can now view spike protection periods

Some of our users have recently requested to view the periods that Spike protection is active. On the Spike protection page of the project settings you'll now see a table listing all period that spike protection was active.

Our docs are now searchable

Our documentation pages can now be easily searched in real-time,

Snooze notifications per application version

In addition to snoozing notifications for a number of occurrences or a fixed period, we have introduced a new way of snoozing errors. You can now snooze errors per application version. In this blog post, you'll learn all about it.

Improving Ignition's security

A few days ago, you might have received a Dependabot security warning on Ignition regarding a remote execution exploit. In this blog post, we'd like to explain why that security warning isn't an issue for most and how we improved Ignition's security.

Flare can now notify you via Discord and Microsoft Teams

We added a couple of new notification channels. In this post you'll also see some actual code from our codebase.

Installing Blackfire on Laravel Vapor

In this blogpost we'll take a quick look at how Blackfire is set-up and how Lambda layers works. In the second part of this post we'll add the two together to get production profiling data from Lambda into Blackfire.

How to safely delete records in massive tables on AWS using Laravel

Recently we had to delete unneeded records in a huge table. In this post, I'd like to show you the challenges we had to overcome and the solutions we came up with.

Introducing JavaScript error tracking

Track Wordpress errors with Flare

Using Flare with Lumen

Creating business opportunities with error tracking

Sending logs to Flare

Introducing "ddd" - a new global helper for Laravel

Today we are very excited to announce a new global helper function to quickly dump, die and debug using Ignition. Introducing ddd!