Fix links to client-reports and envelopes

Author: antonpirker

develop-docs/application/feedback-architecture.mdx

@@ -15,12 +15,12 @@ When broken down, there are **5** ways to create feedback in our system 😵‍
 `FeedbackCreationSource(Enum)` in [create_feedback.py](https://github.com/getsentry/sentry/blob/2b642e149c79b251e1c2f4339fc73d656347d74e/src/sentry/feedback/usecases/create_feedback.py#L33-L33).
 The 4 ways _clients_ can create feedback are:
 
-`NEW_FEEDBACK_ENVELOPE`: [The new format](https://develop.sentry.dev/sdk/envelopes/#full-examples) created by the Replay team when adding
+`NEW_FEEDBACK_ENVELOPE`: [The new format](https://develop.sentry.dev/sdk/data-model/envelopes/#full-examples) created by the Replay team when adding
 the [User Feedback Widget](https://docs.sentry.io/product/user-feedback/#user-feedback-widget)
 to the JavaScript SDK. It allows adding more information, for example tags,
 release, url, etc.
 
-`USER_REPORT_ENVELOPE`: [The older format](https://develop.sentry.dev/sdk/envelopes/#user-feedback) with name/email/comments, that requires
+`USER_REPORT_ENVELOPE`: [The older format](https://develop.sentry.dev/sdk/data-model/envelopes/#user-feedback) with name/email/comments, that requires
 `event_id` to link a Sentry error event.
 
 `USER_REPORT_DJANGO_ENDPOINT`: [The deprecated Web API](https://docs.sentry.io/api/projects/submit-user-feedback/)
@@ -41,7 +41,7 @@ which
 
 ## Feedback events
 
-The new and preferred way to send feedback from the SDK is in an [event envelope](https://develop.sentry.dev/sdk/envelopes/#full-examples).
+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).
 The format is the same as error events, except the `type` header = `"feedback"`. While
 user reports have an associated event, **new feedback _is_ an event**. This
 offers 2 improvements:
@@ -84,7 +84,7 @@ In Relay v24.5.1, we migrated feedback to its own kafka topic + consumer,
 ### Attachments
 
 We only use attachments for the widget’s screenshot feature, which allows users
-to submit **at most 1 screenshot per feedback**. Attachments are another [item type](https://develop.sentry.dev/sdk/envelopes/#attachment)
+to submit **at most 1 screenshot per feedback**. Attachments are another [item type](https://develop.sentry.dev/sdk/data-model/envelopes/#attachment)
 in an envelope.
 
 - SDK v8.0.0+, Relay v24.5.1+: Sends the feedback and attachment items in the same envelope.
@@ -139,7 +139,7 @@ Simplified diagram:
 
 ### Envelopes
 
-User reports are also sent to Relay in [envelope format](https://develop.sentry.dev/sdk/envelopes/#user-feedback).
+User reports are also sent to Relay in [envelope format](https://develop.sentry.dev/sdk/data-model/envelopes/#user-feedback).
 **This item type is misleadingly called “user feedback” in some of our docs, but the
 item header will read `"user_report"`.**
 

develop-docs/sdk/data-model/envelope-items.mdx

@@ -226,7 +226,7 @@ The item contains a user feedback / user report JSON payload:
 
 Item type `"client_report"` contains a client report payload encoded in JSON.
 
-See the <Link to="/sdk/client-reports/">client reports</Link> documentation for the payload
+See the <Link to="/sdk/telemetry/client-reports/">client reports</Link> documentation for the payload
 details.
 
 **Constraints:**

develop-docs/sdk/data-model/event-payloads/index.mdx

@@ -6,7 +6,7 @@ sidebar_order: 3
 Events are the fundamental data that clients, often through the use of an SDK, send
 to the Sentry server.
 
-Events are packed into [envelopes](/sdk/envelopes/) and are sent to the `/api/{PROJECT_ID}/envelope/` API endpoint.
+Events are packed into [envelopes](/sdk/data-model/envelopes/) and are sent to the `/api/{PROJECT_ID}/envelope/` API endpoint.
 
 Sending event payloads to the `/api/{PROJECT_ID}/store/` API endpoint is deprecated.
 
@@ -309,7 +309,7 @@ These limits are subject to future change and defined currently as:
 - *1MB* decompressed (and `200KB` compressed) for events of type `error`
 - *1MB* decompressed (and `200KB` compressed) for events of type `transaction`
 
-Sessions, client reports, replays, check-ins, and profiles are not events and have different size limits. See [Envelope Size Limits](/sdk/envelopes/#size-limits).
+Sessions, client reports, replays, check-ins, and profiles are not events and have different size limits. See [Envelope Size Limits](/sdk/data-model/envelopes/#size-limits).
 
 ## Core Interfaces
 

develop-docs/sdk/data-model/event-payloads/transaction.mdx

@@ -4,11 +4,11 @@ title: Transaction Payloads
 
 Transactions are used to send tracing events to Sentry.
 
-Transactions must be wrapped in an [Envelope](/sdk/envelopes/) and therefore also be sent to the Envelope endpoint.
+Transactions must be wrapped in an [Envelope](/sdk/data-model/envelopes/) and therefore also be sent to the Envelope endpoint.
 
 <Alert title="Note on backwards compatibility" level="info">
   Envelopes are a new format and therefore only work on Sentry >= 10. More
-  information can be found on the <Link to="/sdk/envelopes/">Envelope</Link> page.
+  information can be found on the <Link to="/sdk/data-model/envelopes/">Envelope</Link> page.
 </Alert>
 
 ## Anatomy

develop-docs/sdk/expected-features/data-handling.mdx

@@ -118,5 +118,5 @@ Fields in the event payload that allow user-specified or dynamic values are rest
 
 Additionally, size limits apply to all store requests for the total size of the request, event payload, and attachments. Sentry rejects all requests exceeding these limits. Please refer the following resources for the exact size limits:
 
-- <Link to="/sdk/envelopes/#size-limits">Envelope Endpoint Size Limits</Link>
+- <Link to="/sdk/data-model/envelopes/#size-limits">Envelope Endpoint Size Limits</Link>
 - <Link to="/sdk/store/#size-limits">Store Endpoint Size Limits</Link>

develop-docs/sdk/expected-features/rate-limiting.mdx

@@ -15,7 +15,7 @@ Each *quota_limit* has the form `retry_after:categories:scope:reason_code:namesp
 
 - `retry_after`: Number of seconds (as an integer or a floating point number) until this rate limit expires.
 - `categories`: Semicolon-separated list of [data categories](https://github.com/getsentry/relay/blob/master/relay-base-schema/src/data_category.rs#L91). **If empty, this limit applies to all categories**.
-    While these categories might look similar to the [envelope item types](/sdk/envelopes/#data-model), they are not identical, and have slight differences.
+    While these categories might look similar to the [envelope item types](/sdk/data-model/envelopes/#data-model), they are not identical, and have slight differences.
 - `scope`: The scope that this limit applies to. Can be ignored by SDKs.
 - `reason_code`: A unique identifier for the quota hinting at the rate limiting reason. Can be ignored by SDKs.
 - `namespaces`: Semicolon-separated list of metric namespace identifiers. This will only be present if the rate limit applies to the `metric_bucket` data category. If the namespace is not present, the backoff applies to all metrics.
@@ -83,7 +83,7 @@ Guidelines for how SDKs should determine the current rate limits:
 As stated earlier, SDKs can ignore the `scope` dimension. These definitions are here as a suplement to explain what the `X-Sentry-Rate-Limits` header is made of.
 
 - **Category:** Classifies the type of data that is being counted. Arbitrary categories can be added as long as they can be inferred from the event or data being ingested.
-While these [data categories](https://github.com/getsentry/relay/blob/master/relay-base-schema/src/data_category.rs#L91) might look similar to the [envelope item types](/sdk/envelopes/#data-model), they are not identical, and have slight differences.
+While these [data categories](https://github.com/getsentry/relay/blob/master/relay-base-schema/src/data_category.rs#L91) might look similar to the [envelope item types](/sdk/data-model/envelopes/#data-model), they are not identical, and have slight differences.
   - `default`: Events with an event_type not listed explicitly below.
   - `error`: Error events.
   - `transaction`: Transaction type events.

develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx

@@ -389,8 +389,8 @@ It's suggested to remove unnecessary data like thread data without samples from
 ## Ingestion
 
 After this payload is generated, serialize it as JSON, pack it into the same
-[Envelope](/sdk/envelopes/) as the associated transaction with the item type
-[`profile`](/sdk/envelopes/#profile) and send it to Relay.
+[Envelope](/sdk/data-model/envelopes/) as the associated transaction with the item type
+[`profile`](/sdk/data-model/envelopes/#profile) and send it to Relay.
 
 This envelope should look like this:
 

develop-docs/sdk/telemetry/profiles/sample-format-v2.mdx

@@ -283,7 +283,7 @@ It's suggested to remove unnecessary data like thread data without samples from
 
 After this payload is generated, serialize it as JSON, pack it into an
 
-[Envelope](/sdk/envelopes/) with the item type [`profile_chunk`](/sdk/envelopes/#profile-chunk) and send
+[Envelope](/sdk/data-model/envelopes/) with the item type [`profile_chunk`](/sdk/data-model/envelopes/#profile-chunk) and send
 
 it to Relay.
 

develop-docs/sdk/telemetry/sessions/index.mdx

@@ -9,7 +9,7 @@ Looking for Sentry's **Session Replay**? Click <a class href="https://docs.sentr
 
 </Note>
 
-For basic health tracking Sentry accepts <Link to="/sdk/envelopes/">envelopes</Link>
+For basic health tracking Sentry accepts <Link to="/sdk/data-model/envelopes/">envelopes</Link>
 containing session update events. These session update events can be used to
 inform Sentry about release and project associated project health.
 

develop-docs/sdk/telemetry/traces/index.mdx

@@ -139,7 +139,7 @@ tree as well as the unit of reporting to Sentry.
   - `super.finish()` (call finish on Span)
   - Send it to Sentry only if `sampled == true`
   - Like spans, can be given an optional `endTimestamp` value that should be passed into the `span.finish()` call
-  - A `Transaction` needs to be wrapped in an `Envelope` and sent to the [Envelope Endpoint](/sdk/envelopes/)
+  - A `Transaction` needs to be wrapped in an `Envelope` and sent to the [Envelope Endpoint](/sdk/data-model/envelopes/)
   - The `Transport` should use the same internal queue for `Transactions` / `Events`
   - The `Transport` should implement category-based rate limiting →
   - The `Transport` should deal with wrapping a `Transaction` in an `Envelope` internally