Create a Sentry Project
In this tutorial, you create a new project in your Sentry account. Projects allow you to scope events to a distinct application in your organization and assign responsibility and ownership to specific users and teams within your organization. You can create a project for a particular language or framework used in your application. For example, you might have separate projects for your API server and frontend client. For more information see best practices for creating projects
Log in to your Sentry organization.
Select "Projects" from the left side navigation menu to display the list of all your projects.
Click on the "+ Create Project" button.
If there are no projects in your account, you might be redirected to the onboarding wizard to create your first project.
Give the project a name in the "Project name" field.
Under "Set your default alert settings", select "I'll create my own alerts later".
Assign a "Team" to the project.
If you haven't defined any teams, you can either select the default org team (the team that has the same name as your Sentry org) or click on the "+" button to create a new team.
Click "Create Project". This takes you to the configuration page. Read through the quick Getting Started guide.
Copy the "DSN" key and keep it handy as you will be copying the key into the source code.
The DSN (or Data Source Name) tells the SDK where to send the events, associating them with the project you just created.
Click on the "Got it!" button at the bottom to create the project.
You can create various alert rules for each project and let Sentry know when, how, and whom you want to notify when errors occur in your application. Alert rules consist of conditions and actions, which are performed when the associated conditions are met. When creating a new project, you can choose to create it with an alert rule that notifies all project team members (by email) the first time a new issue appears. This means that the next time a similar error occurs, the notification is not triggered since the error is not "new".
In this step, you create a new alert rule that notifies every time an event occurs, even if it's associated with an already existing issue. In a real-life scenario you'd probably add additional conditions, as you wouldn't want to be notified every time an event happens in your frontend code on your end user's browsers.
From the project drop down list, find the new project and click on the cog icon to open the project settings.
Click "Alerts" to open the alerts configuration page.
Click "New Alert Rule".
In the new alert rule form, select "Issue Alert" as the type and enter the following values:
The new alert rule notifies the selected team members every time an event is seen in All Environments by Mail
Click "Save Rule" to create the new rule.