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
Login to your Sentry organization
Projectsfrom the left side navigation menu to display the list of all your projects
Click on the
+ Create Projectbutton
Note: If there are no projects in your account --- you might be redirected to the onboarding wizard to create your first project.
Select the language or framework for your project based on the code you wish to monitor --- in this case,
Give the project a
Set your default alert settingscheck
i'll create my own alerts later
Assign a Teamto 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.
Create Project. This takes you to the configuration page. Read through the quick Getting Started guide.
DSN keyand keep it handy as we 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 per 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. For more information, see Alerts. When creating a new project, you can select to create it with an alert rule that notifies all project team members (via 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 notifying 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
Alertsto open the Alerts Configuration page
New Alert Rule
In the New Alert Rule form, select an
Issue Alerttype and enter the following values
The new alert rule notifies the selected team members every time an event is seen in All Environments via Mail
Save Ruleto create the new rule