Getting started with Flare
You can try Flare by registering an account to start your free 10-day trial.
After creating your account, we'll guide you through the steps required for the kind of app you are building.
When creating your first project you need to:
- Pick a name for your project (e.g. "Flare")
- Optionally, you can group the project (e.g. "Flare")
- An environment (e.g. "Production"), please note Flare won't enforce this environment, it is perfectly possible to send staging errors to a production project.
- And the technology you are using
We support:
- generic PHP apps
- generic JavaScript apps
- Laravel 6 to the latest version, we also support Laravel Vapor
- Vue from v2 to the latest version
- React
After you've picked your type of app, we'll display detailed instructions on configuring your app to send errors to Flare.
After you've set this up, it's probably a good idea to configure notifications to choose how we should notify you when an error happens in your app.
Congrats, you've now set up your first project! If you have another application of which you want to track the errors, you can create a new project.
Structuring projects
Flare allows you to group projects. This is useful if multiple projects are part of the same application. For example, you might have a Laravel backend and a Vue frontend, and both these technologies have a staging and production environment. You can group these projects together to get a better overview of your application.
When building applications, we like to use the following structure in, for example, the Flare group:
- name: Flare | technology: Laravel | environment: production
- name: Flare | technology: Laravel | environment: staging
- name: Flare | technology: React | environment: production
- name: Flare | technology: React | environment: staging
Creating a group for each technology allows you to quickly see which technology is causing the most errors. By creating a group for each environment, you can easily see which environment is causing the most errors.
