Skip to content

Commit 907e187

Browse files
authored
chore(dsn): update reference to dsn settings from settings -> client keys to settings -> sdk setup -> client keys (#13980)
1 parent d17d325 commit 907e187

File tree

7 files changed

+10
-10
lines changed

7 files changed

+10
-10
lines changed

docs/concepts/key-terms/dsn-explainer.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ If an SDK is not initialized or if it is initialized with an empty DSN, the SDK
1818

1919
DSNs are safe to keep public because they only allow submission of new events and related event data; they do not allow read access to any information.
2020

21-
While there is a risk of abusing a DSN, where any user can send events to your organization with any information they want, this is a rare occurrence. Sentry provides controls to [block IPs](/platform-redirect/?next=/configuration/options/) and similar concerns. You can also rotate (and revoke) DSNs by navigating to **[Project] > Settings > Client Keys (DSN)**.
21+
While there is a risk of abusing a DSN, where any user can send events to your organization with any information they want, this is a rare occurrence. Sentry provides controls to [block IPs](/platform-redirect/?next=/configuration/options/) and similar concerns. You can also rotate (and revoke) DSNs by navigating to **[Project] > Settings > SDK Setup > Client Keys (DSN)**.
2222

2323
If your application is shipped to client devices, if possible, we recommend having a way to configure the DSN dynamically. In an ideal scenario, you can "ship" a new DSN to your application without the customer downloading the latest version. We recognize that this may not always be practical, but we cannot offer further advice as this scenario is implementation specific.
2424

@@ -28,7 +28,7 @@ If you're in the process of setting up a project, you can find your DSN in the i
2828

2929
![DSN in code snippet](./img/create-new-project-04.png)
3030

31-
You can also find the DSN in your project settings by navigating to **[Project] > Settings > Client Keys (DSN)** in [sentry.io](https://sentry.io/).
31+
You can also find the DSN in your project settings by navigating to **[Project] > Settings > SDK Setup > Client Keys (DSN)** in [sentry.io](https://sentry.io/).
3232

3333
### The Parts of the Data Source Name (DSN)
3434

docs/organization/getting-started/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ Automatic issue management is available only if your organization is on a Busine
8989

9090
## 4. Create Projects
9191

92-
To start monitoring errors in your app with Sentry, you'll need to initialize the SDK with a DSN key. To obtain a key, add a new Sentry project by going to **Projects** and clicking "Create Project". Give the project a name and assign the responsible [team (or teams)](#2-set-up-teams). Then, retrieve the key in **[Project] > Settings > Client Keys (DSN)**.
92+
To start monitoring errors in your app with Sentry, you'll need to initialize the SDK with a DSN key. To obtain a key, add a new Sentry project by going to **Projects** and clicking "Create Project". Give the project a name and assign the responsible [team (or teams)](#2-set-up-teams). Then, retrieve the key in **[Project] > Settings > SDK Setup > Client Keys (DSN)**.
9393

9494
![Retrieve your project DSN key.](./img/project-dsn.png)
9595

docs/pricing/quotas/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Events and attachments that exceed your quota will not be accepted, so you may w
6666

6767
### Rate Limits
6868

69-
You can add limits for error events on a per-project basis in **[Project] > Settings > Client Keys (DSN)**. If the event rate limit for a project has been exceeded, and your subscription allows, the event won't be counted. You can also rate limit attachments on an organization level in **Settings > Security & Privacy**. Learn more in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/#rate-limiting) and [Manage Your Attachments Quota](/pricing/quotas/manage-attachments-quota/#rate-limiting).
69+
You can add limits for error events on a per-project basis in **[Project] > Settings > SDK Setup > Client Keys (DSN)**. If the event rate limit for a project has been exceeded, and your subscription allows, the event won't be counted. You can also rate limit attachments on an organization level in **Settings > Security & Privacy**. Learn more in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/#rate-limiting) and [Manage Your Attachments Quota](/pricing/quotas/manage-attachments-quota/#rate-limiting).
7070

7171
### Event Repetition
7272

docs/pricing/quotas/manage-event-stream-guide.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ We strongly recommend that you make subscription changes **before** the last day
121121

122122
Rate limiting allows you to set the maximum volume of error events a project key will accept during a period of time. For example, if you have a project in production that generates a lot of noise, a rate limit allows you to set the maximum amount of data, such as “500 events per minute”. Additionally, you can create a second key for the same project for your staging environment, which is unlimited, ensuring your QA process is still untouched.
123123

124-
In **[Project] > Settings > Client Keys (DSN)**, click "Configure", and you can create multiple DSN keys per project and assign different (or no) rate limits to each key. This will allow you to dynamically allocate keys (with varying thresholds) depending on release, environment, and so on.
124+
In **[Project] > Settings > SDK Setup > Client Keys (DSN)**, click "Configure", and you can create multiple DSN keys per project and assign different (or no) rate limits to each key. This will allow you to dynamically allocate keys (with varying thresholds) depending on release, environment, and so on.
125125

126126
![Per DSN Key rate limits](./img/manage-event-stream-11.png)
127127

@@ -133,7 +133,7 @@ While rate limiting is quite useful for managing your monthly event quota, keep
133133

134134
A good way to set a project rate limit is by figuring out the expected event volume based on your average traffic. Here's how to do that:
135135

136-
1. Go **[Project] > Settings > Client Keys (DSN)** and open the project DSN key configuration under by clicking "Configure".
136+
1. Go **[Project] > Settings > SDK Setup > Client Keys (DSN)** and open the project DSN key configuration under by clicking "Configure".
137137
1. In the "KEY USAGE IN THE LAST 30 DAYS" graph, look for the highest point, or the maximum daily rate. In the example below, the maximum daily rate in the last month is less than 34K:
138138
![Calculating rate limits](./img/manage-event-stream-14-new.png)
139139
{/*<!-- image notes: Sentry, airflow, Santry, app-frontend -->*/}

docs/product/sentry-basics/distributed-tracing/create-new-project.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Follow the steps below to create a new Sentry project for a sample React applica
2828

2929
- Click **Create Project**. This takes you to the quick Configure React SDK guide, which provides an overview of how to configure the SDK. This tutorial covers the SDK setup in more detail.
3030

31-
- You'll notice that the Sentry React SDK setup code has come pre-populated with the project's unique DSN (Data Source Name). The DSN tells the SDK where to send events, so events are associated with the right project. You'll need to paste the DSN key into the SDK configuration code later in the tutorial. You can make a note of it now, or you can also find a project's DSN anytime in **[Project] > Settings > Client Keys (DSN)**
31+
- You'll notice that the Sentry React SDK setup code has come pre-populated with the project's unique DSN (Data Source Name). The DSN tells the SDK where to send events, so events are associated with the right project. You'll need to paste the DSN key into the SDK configuration code later in the tutorial. You can make a note of it now, or you can also find a project's DSN anytime in **[Project] > Settings > SDK Setup > Client Keys (DSN)**
3232

3333
1. Click **Take me to Issues** to go to your new project's **Issues** page.
3434

@@ -58,7 +58,7 @@ Next, follow the steps below to create a new Sentry project for a sample Backend
5858

5959
1. Copy the DSN key and keep it handy.
6060

61-
> You can also find a project's DSN anytime in **[Project] > Settings > Client Keys (DSN)**.
61+
> You can also find a project's DSN anytime in **[Project] > Settings > SDK Setup > Client Keys (DSN)**.
6262
6363
1. Click **Take me to Issues** to go to your new project's **Issues** page.
6464

docs/product/sentry-basics/integrate-backend/getting-started.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Follow the steps below to create a new Sentry project for a sample Django applic
4747

4848
1. Copy the DSN key and keep it handy. Each project has a unique DSN (Data Source Name). The DSN tells the SDK where to send events, so events are associated with the right project. You'll need to paste the DSN key into your source code later so the errors generated in this tutorial go to your new project.
4949

50-
> You can also find a project's DSN anytime in **[Project] > Settings > Client Keys (DSN)**.
50+
> You can also find a project's DSN anytime in **[Project] > Settings > SDK Setup > Client Keys (DSN)**.
5151
5252
## Step 2: Get the Code
5353

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Follow the steps below to create a new Sentry project for a sample React applica
3030

3131
1. Copy the DSN key and keep it handy. Each project has a unique DSN (Data Source Name). The DSN tells the SDK where to send events, so events are associated with the right project. You'll need to paste the DSN key into your source code later so the errors generated in this tutorial go to your new project.
3232

33-
> You can also find a project's DSN anytime in **[Project] > Settings > Client Keys (DSN)**.
33+
> You can also find a project's DSN anytime in **[Project] > Settings > SDK Setup > Client Keys (DSN)**.
3434
3535
1. Click **Take me to Issues** to go to your new project's **Issues** page.
3636

0 commit comments

Comments
 (0)