You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/[[...path]]/page.tsx
+6-2Lines changed: 6 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -200,10 +200,14 @@ export async function generateMetadata(props: MetadataProps): Promise<Metadata>
200
200
: domain;
201
201
lettitle=
202
202
'Sentry Docs | Application Performance Monitoring & Error Tracking Software';
203
-
letcustomCanonicalTag;
203
+
letcustomCanonicalTag: string='';
204
204
letdescription=
205
205
'Self-hosted and cloud-based application performance monitoring & error tracking that helps software teams see clearer, solve quicker, & learn continuously.';
data-modal-disclaimer="Please note: This is a tool that searches publicly available sources. Do not include any sensitive or personal information in your queries. For more on how Sentry handles your data, see our [Privacy Policy](https://sentry.io/privacy/)."
60
+
data-modal-example-questions="How to set up Sentry for Next.js?,What are tracePropagationTargets?"
Copy file name to clipboardExpand all lines: develop-docs/application-architecture/feedback-architecture.mdx
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,17 +11,17 @@ It will:
11
11
12
12
## Creation sources
13
13
14
-
When broken down, there are **5** ways to create feedback in our system 😵💫.
15
-
(But 4 of them, related to user reports, are quite similar!) A good reference is the
14
+
When broken down, there are **4** ways to create feedback in our system, with
15
+
3 sharing the same data model. A good reference is the
16
16
`FeedbackCreationSource(Enum)` in [create_feedback.py](https://github.com/getsentry/sentry/blob/2b642e149c79b251e1c2f4339fc73d656347d74e/src/sentry/feedback/usecases/create_feedback.py#L33-L33).
17
17
The 4 ways _clients_ can create feedback are:
18
18
19
-
`NEW_FEEDBACK_ENVELOPE`: [The new format](https://develop.sentry.dev/sdk/data-model/envelopes/#full-examples) created by the Replay team when adding
19
+
`NEW_FEEDBACK_ENVELOPE`: [The new format](/sdk/data-model/envelope-items/#user-feedback) created by the Replay team when adding
20
20
the [User Feedback Widget](https://docs.sentry.io/product/user-feedback/#user-feedback-widget)
21
21
to the JavaScript SDK. It allows adding more information, for example tags,
22
22
release, url, etc.
23
23
24
-
`USER_REPORT_ENVELOPE`: [The older format](https://develop.sentry.dev/sdk/data-model/envelope-items/#user-feedback) with name/email/comments, that requires
24
+
`USER_REPORT_ENVELOPE`: [The older format](/sdk/data-model/envelope-items/#user-report) with name/email/comments, that requires
25
25
`event_id` to link a Sentry error event.
26
26
27
27
`USER_REPORT_DJANGO_ENDPOINT`: [The deprecated Web API](https://docs.sentry.io/api/projects/submit-user-feedback/)
@@ -31,7 +31,7 @@ release, url, etc.
31
31
## How feedback is stored
32
32
33
33
On the backend, each feedback submission in Sentry's UI is **an un-grouped issue occurrence**,
34
-
saved via the [issues platform](https://develop.sentry.dev/issue-platform/).
34
+
saved via the [issues platform](/issue-platform/).
35
35
The entrypoint is [**`create_feedback_issue()`**](https://github.com/getsentry/sentry/blob/2b642e149c79b251e1c2f4339fc73d656347d74e/src/sentry/feedback/usecases/create_feedback.py#L184-L184),
36
36
which
37
37
@@ -42,7 +42,7 @@ which
42
42
43
43
## Feedback events
44
44
45
-
The new and preferred way to send feedback from the SDK is in an [event envelope](https://develop.sentry.dev/sdk/data-model/envelopes/#full-examples).
45
+
The preferred way of sending feedback from the SDK is in [feedback envelope](/sdk/data-model/envelope-items/#user-feedback).
46
46
The format is the same as error events, except the `type` header = `"feedback"`. While
47
47
user reports have an associated event, **new feedback _is_ an event**. This
48
48
offers 2 improvements:
@@ -94,7 +94,7 @@ In Relay v24.5.1, we migrated feedback to its own kafka topic + consumer,
94
94
### Attachments
95
95
96
96
We only use attachments for the widget’s screenshot feature, which allows users
97
-
to submit **at most 1 screenshot per feedback**. Attachments are another [item type](https://develop.sentry.dev/sdk/data-model/envelopes/#attachment)
97
+
to submit **at most 1 screenshot per feedback**. Attachments are another [item type](/sdk/data-model/envelopes/#attachment)
98
98
in an envelope.
99
99
100
100
- SDK v8.0.0+, Relay v24.5.1+: Sends the feedback and attachment items in the same envelope.
@@ -186,9 +186,7 @@ graph TD
186
186
187
187
### Envelopes
188
188
189
-
User reports are also sent to Relay in [envelope format](https://develop.sentry.dev/sdk/data-model/envelope-items/#user-feedback).
190
-
**This item type is misleadingly called “user feedback” in some of our docs, but the
191
-
item header will read `"user_report"`.**
189
+
User reports are also sent to Relay in envelope format, item type [user_report](/sdk/data-model/envelope-items/#user-report).
192
190
193
191
The SDK function that sends these is `captureUserFeedback`.
Copy file name to clipboardExpand all lines: develop-docs/backend/application-domains/database-migrations/index.mdx
-11Lines changed: 0 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,17 +91,6 @@ To run the test locally, run `pytest` with `--migrations` flag. For example, `py
91
91
92
92
If you would like to speed up the migration tests and do not require rebuilding the databases on each test run, supply `--reuse-db` as an additional option to the test command.
93
93
94
-
### Backup Testing
95
-
When you add or change a model, an error message in CI may appear explaining that one or multiple tests "produced an `export.json` backup file that was missing the above models".
96
-
In order to resolve this, there are two steps:
97
-
1. Add the new or modified model to the exhaustive organization in [testutils/helpers/backups.py](https://github.com/getsentry/sentry/blob/f9e6aa610340fd41cc13490aeda71b06bbc933c2/src/sentry/testutils/helpers/backups.py#L366) by creating an instance of your model, for example by invoking MyModel.objects.create(). This ensures the presence of the new model when creating the snapshot and during testing.
98
-
2. The snapshot files can be regenerated using the following command:
There are also tests for model dependencies that make use of automatically generated fixtures in tests/sentry/backup/test_dependencies.py. These tests will fail if they are not updated when a new model with dependencies on other models is added, or dependencies are modified. In order to re-generate the model dependency graphs, you can run [bin/generate-model-dependency-fixtures](https://github.com/getsentry/sentry/blob/f9e6aa610340fd41cc13490aeda71b06bbc933c2/bin/generate-model-dependency-fixtures).
104
-
105
94
#### Notes
106
95
107
96
- There is a [known issue](https://github.com/getsentry/sentry/blob/e4627f093de4718e054ba9c6b002ff0b9a5b6033/tests/sentry/migrations/test_0295_backfill_alertrule_type.py#L1-L3) with the `django-pg-zero-downtime-migrations` package which causes the roll back of a `NOT NULL` constraint to fail.
0 commit comments