Skip to content

Commit 4ab132a

Browse files
committed
addressing comments updating screenshots
1 parent 53f5110 commit 4ab132a

File tree

4 files changed

+14
-14
lines changed

4 files changed

+14
-14
lines changed
Loading

src/docs/product/alerts/create-alerts/issue-alert-config.mdx

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -18,15 +18,7 @@ The “Environment” dropdown list here has the same environments that are avai
1818

1919
## Project
2020

21-
Specify which project will use this particular alert rule. Created alert rule will only process events from this project.
22-
23-
## Alert Name
24-
25-
Give your alert a descriptive name, such as the team affected and the topic of the alert. For example, "Frontend Latency", "Backend Failure Rate", or "Billing Apdex".
26-
27-
## Team
28-
29-
You can choose a team to associate with an alert so that members of that team can edit the alert. Note that you can only make this association if you are a member of the team. If no team is selected, anyone can edit the alert.
21+
Specify which project will use this particular alert rule. The created alert rule will only process events from this project.
3022

3123
## "When" Conditions: Triggers
3224

@@ -124,6 +116,14 @@ The available intervals are:
124116
- Hours: 3, 12, 24
125117
- Days: 7, 30
126118

119+
## Alert Name
120+
121+
Give your alert a descriptive name, such as the team affected and the topic of the alert. For example, "Frontend Latency", "Backend Failure Rate", or "Billing Apdex".
122+
123+
## Team
124+
125+
You can choose a team to associate with an alert so that members of that team can edit the alert. Note that you can only make this association if you are a member of the team. If no team is selected, anyone can edit the alert.
126+
127127
## Project-Level Alert Settings
128128

129129
In **[Project] > Settings > Alerts**, you can configure alert email subject templates and digest settings. Sentry users with owner, manager, or admin permissions and above can change these default notification settings.

src/docs/product/alerts/create-alerts/metric-alert-config.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -54,16 +54,16 @@ Choose the time period over which to evaluate your metric. Your choices range be
5454

5555
The following set of filters translates into a [Discover query](/product/discover-queries/) that is displayed in the chart at the top of the alert configuration page.
5656

57+
### Project
58+
59+
Specify which project will use this particular alert rule. Created alert rule will only process events from this project.
60+
5761
### Environment
5862

5963
Specify which <PlatformLink to="/configuration/environments/">environment(s)</PlatformLink> will use this particular alert rule. This control filters on the `environment` tag in your events. This filter is helpful because the urgency and workflows you apply to production alerts might differ from those you apply to alerts originating from your QA environment, for example.
6064

6165
The “Environment” dropdown list here has the same environments that are available for the selected project in the common “Environment” filter dropdown (this does not include hidden environments). Selecting "All Environments" is equivalent to having no environment filter.
6266

63-
## Project
64-
65-
Specify which project will use this particular alert rule. Created alert rule will only process events from this project.
66-
6767
### Event Type
6868

6969
For some metric alerts, you can set the event type that you want to be alerted about in the “Events” dropdown:
@@ -94,7 +94,7 @@ This feature is available only if your organization is on either a Business or T
9494

9595
</Note>
9696

97-
Change alerts, or alerts that use a percent change threshold, are useful when you want to know if a metric is significantly different from normal. To do this, you’ll need to set the time period to compare to. One example would be comparing the number of errors in the last hour to the same time period one week ago. If errors are 25% higher in the last hour than they were in the same period a week ago, then an alert will trigger.
97+
Change alerts, or alerts that use a percent change threshold, are useful when you want to know if a metric is significantly different from normal. To do this, you’ll need to pick a metric period and time interval to compare. One example would be comparing the number of errors in the last hour to the same time period one week ago. If errors are 25% higher in the last hour than they were in the same period a week ago, then an alert will trigger.
9898

9999
![When the percent change option is selected.](percent-change.png)
100100

Loading

0 commit comments

Comments
 (0)