Skip to content

Commit 17a7e17

Browse files
authored
update alert rule language (#4668)
* updated alert rule directions to match current language and old screenshots * fixed screenshot and formatting
1 parent c44132b commit 17a7e17

File tree

8 files changed

+21
-15
lines changed

8 files changed

+21
-15
lines changed
120 KB
Loading
157 KB
Loading
145 KB
Loading
128 KB
Loading

src/docs/product/sentry-basics/integrate-frontend/create-new-project.mdx

Lines changed: 21 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -13,21 +13,21 @@ In this tutorial, you create a new _project_ in your Sentry account. Projects al
1313

1414
1. Log in to your [Sentry organization](https://sentry.io).
1515

16-
2. Select "Projects" from the left side navigation menu to display the list of all your projects.
16+
1. Select **Projects** from the left side navigation menu to display the list of all your projects.
1717

18-
3. Click on the "+ Create Project" button.
18+
1. Click on the "+ Create Project" button.
1919

2020
![Create new project](create-new-project-01.png)
2121

2222
> If there are no projects in your account, you might be redirected to the onboarding wizard to create your first project.
2323
24-
- Select the language or framework for your project based on the code you wish to monitor — in this case, "JavaScript".
24+
- Select the language or framework for your project based on the code you wish to monitor — in this case, "React".
2525

2626
- Give the project a name in the "Project name" field.
2727

2828
- Under "Set your default alert settings", select "I'll create my own alerts later".
2929

30-
- Assign a "Team" to the project.
30+
- Assign a team to the project by selecting one in the "Team" dropdown.
3131

3232
![Select project language](create-new-project-02.png)
3333

@@ -37,37 +37,43 @@ In this tutorial, you create a new _project_ in your Sentry account. Projects al
3737

3838
- Click "Create Project". This takes you to the configuration page. Read through the quick Getting Started guide.
3939

40-
4. Copy the "DSN" key and keep it handy as you will be copying the key into the source code.
40+
1. Copy the "DSN" key and keep it handy as you will be copying the key into the source code. You can also find this information any time in **[Project] > Settings > Client Keys (DSN)**.
4141

4242
![Copy DSN](create-new-project-04.png)
4343

4444
> The DSN (or Data Source Name) tells the SDK where to send the events, associating them with the project you just created.
4545
46-
5. Click on the "Got it!" button at the bottom to create the project.
46+
1. Click on the "Got it!" button at the bottom to create the project.
4747

4848
## Step 2: Create an alert rule
4949

5050
You can create various [alert rules](/product/alerts-notifications/alerts/) 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".
5151

5252
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.
5353

54-
1. From the project drop down list, find the new project and click on the cog icon to open the project settings.
54+
1. Select **Alerts** in the left side menu.
5555

56-
![Open Project Settings](generate-first-error-07.png)
56+
1. Click "Create Alert".
5757

58-
2. Click "Alerts" to open the alerts configuration page.
58+
![Alerts Configuration](generate-first-error-08.png)
5959

60-
3. Click "New Alert Rule".
60+
> If your project isn't already selected, you'll be prompted to do that before you start rule setup.
6161
62-
![Alerts Configuration](generate-first-error-08.png)
62+
1. Select "Issues" as the alert type and click "Set Conditions".
63+
64+
![Alert types](generate-first-error-10.png)
6365

64-
4. In the new alert rule form, select "Issue Alert" as the type and enter the following values:
66+
1. Enter the following values:
67+
- In the "Environment" field, select "All Environments"
68+
- Enter "Alerts on All Events" in the "Alert name" field
69+
- Under "THEN" conditions, select "Send notification to Issue Owners, Team, or Member", and then "Team" in the dropdown list that's displayed; select your team
70+
- Set the action interval to five minutes
6571

66-
![New Alert Rule form](generate-first-error-09.png)
72+
![New Alert Rule form](generate-first-error-09.png)
6773

68-
> The new alert rule notifies the selected team members every time _an event is seen_ in _All Environments_ by _Mail_
74+
> The new alert rule notifies the selected team members every time _an event is captured_ in _All Environments_. By default, the notification will be sent by email, but you can change your team notification settings in the "Notifications" tab of **Settings > Teams > [Team]**.
6975
70-
5. Click "Save Rule" to create the new rule.
76+
1. Click "Save Rule" to create the new rule.
7177

7278
## Next
7379

107 KB
Loading
107 KB
Loading
222 KB
Loading

0 commit comments

Comments
 (0)