Errors will inevitably occur in your application. There is no way around it. If you notice them while working locally, you can fix them immediately. However, if your application is already live, it gets more tricky because you are not the only person triggering errors anymore. This is where error tracking software like Flare comes in handy.
Picture this: a bunch of developers, most of them back-enders, are given a Figma design file to turn into the new homepage for Flare. We set out to build our brand-new marketing site with a sprinkle of animations. Here is how we crafted them.
Secret secrets are no fun, secret secrets hurt someone... unless they're managed right in your Laravel deployment! Say goodbye to plaintext perils and .env file follies. For Flare we explored some alternative solutions like config servers, the env:encrypt command and git-secret to keep your production environment variables safe and sound. Using git-secret's with user-specific access control and PGP encryption, managing environment variables becomes a breeze.
Today, we're adding AI-powered solutions to Flare. This means we can suggest a solution for almost any error: the AI will likely suggest a helpful suggestion for most errors.
We're still working on our redesign and are close to release. Today we started tackling an issue where the performance of the error page was too slow for us. In the end, we needed to change the structure of the error occurrences table, which is a lot harder than it seems.
As of today, Flare can notify you via Telegram. In this blog post, you'll see that we didn't only provide basic support but also went all the way with notification actions.
We've recently added a support form bubble form to our app. In this post we'll explain what it is, why we added it, and how you can add one to your app.
Flare runs on a few different servers that each produce their own logs. In this post, you'll learn how we can combine multiple logs in a single stream.
We've now have a completely renewed billing experience powered by the latest version of Laravel Spark. In this blog post, we'll share why and how we performed this migration.
Like most SaaS companies, the Flare back-office features a neat dashboard showing some of our key metrics. Using Laravel Nova it's pretty easy to aggregate data per model like the total number of errors or the active subscriptions per week. Behind the scenes these dashboard tiles and graphs use simple database queries. For example, the number of active subscriptions is a simple `SELECT COUNT(*)` query on the `subscriptions` table. But how do we query new subscriptions per week?
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
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.
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.